Integration

NeetoInvoice integration

NeetoInvoice is neeto's time tracking and invoicing tool. Manage clients and projects (billing method, rates, tasks), log and list unbilled time entries, generate invoices from time entries, services, expenses or fixed-price projects (with taxes), email them to the client's recipients, and list invoices with their paid and due amounts. Team members, project users, client recipients, PTO, payroll and timesheet reports are not exposed (they hold people's names, emails and pay data), and client postal addresses are not written. Several writes need the email of the acting NeetoInvoice user. Lists without page or page_size return every record at once. Requests over the rate limit answer HTTP 429 (the limit is not published). Authentication is a workspace API key (type General) sent in the X-Api-Key header, on your workspace subdomain.

Connect NeetoInvoice How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in NeetoInvoice.Built from the 13 NeetoInvoice tools below, on the connection you add once.

What you can do with NeetoInvoice

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Client, 4 operations

create_clientCreate clientPOSTCreates a client with a name, currency and status. Returns its client_id; add invoice recipients in NeetoInvoice before emailing invoices.
get_clientGet clientGETReturns one client: names, currency, status, default due days, notes, logo and the interval of its last invoice. The client's recipients (names and emails) are not returned.
list_clientsList clientsGETLists clients ordered by name, with status, currency and default due days. Without page or page_size every client comes back at once; with them, 30 per page by default, up to 100.
update_clientUpdate clientPATCHChanges a client's name, secondary name, currency, status (active or archived), default due days or notes. Send only the fields to change.

Project, 4 operations

create_projectCreate projectPOSTCreates a project for a client with its billing method and tasks. Returns the project with its id. Users are assigned to projects in NeetoInvoice.
get_projectGet projectGETReturns one project with its client, billing method and rates, recurring invoice settings and invoice count, plus its tasks (ids for create_time_entry) and checklists.
list_projectsList projectsGETLists projects ordered by name, with billing method, rates and status. Without page or page_size every project comes back at once; with them, 30 per page by default, up to 100.
update_projectUpdate projectPATCHChanges a project: name, billing, rates, currency, notes, rounding, locking, approvals or tasks. Only passed parameters are sent; the docs do not say if omitted fields are kept, so read it with get_project first.

Invoice, 2 operations

generate_invoiceGenerate invoicePOSTGenerates an invoice for a client in the background (status generating) from time entries, services, expenses or fixed-price projects. With send_email true it is emailed to the client's recipients.
list_invoicesList invoicesGETLists invoices, newest issue date first, 30 per page by default (up to 100), with totals, amounts paid and due, and days overdue. Deleted invoices are left out.

Time entry, 2 operations

create_time_entryCreate time entryPOSTLogs hours on a project task for a NeetoInvoice user on a given date. Returns the entry with its id and status.
list_time_entriesList time entriesGETLists the unbilled time entries of a project (entries on billed invoices are left out), 30 per page by default. Ids feed generate_invoice. Users appear by id only.

Send, 1 operation

send_invoiceSend invoicePOSTEmails a generated invoice to every current recipient of the client for real and marks it as sent. Returns the invoice number and sent date.

Use NeetoInvoice from Claude Code, Cursor or Codex

Connect NeetoInvoice in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its NeetoInvoice operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect NeetoInvoice

Create your workspace
Sign up free. Nothing to install.
Connect NeetoInvoice once
Add your NeetoInvoice connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.