Local MCP · Invoicer 2.4

Your invoices, connected to your assistant.

Track work, review invoice drafts and export PDFs from the assistant you already use. Connect directly on your computer.

Start with your workspace

Install Invoicer 2.4 or later, open it and select the workspace you want your assistant to use.
Choose a connection method below, then add it to your assistant.
Restart the assistant’s MCP connection. Ask “Use Invoicer to show my clients” and check that an Invoicer tool returns your clients.

Use the desktop launcher

Open Settings → Integrations in Invoicer. Install the command line launcher and copy its configuration. It includes the absolute command path and needs no separate Node.js installation.

Or use the npm examples

The copyable examples below use @invoicer/cli@2.4.0. Install Node.js 22.18 or later, then run this once to check the CLI is ready.

npx -y @invoicer/cli@2.4.0 --version

Use one method per assistant. No separate Invoicer account or API key is needed. If you already have MCP servers, merge the invoicer entry into your configuration.

Codex

Run this in a terminal. Codex CLI and the Codex desktop app share the same MCP configuration.

codex mcp add invoicer -- npx -y @invoicer/cli@2.4.0 mcp

Prefer editing the config file?

Add this to ~/.codex/config.toml. For the desktop launcher, use the command and arguments copied from Invoicer instead.

[mcp_servers.invoicer]
command = "npx"
args = ["-y","@invoicer/cli@2.4.0","mcp"]
startup_timeout_sec = 60

Restart Codex, check that Invoicer appears in its MCP tools and try the read-only clients prompt above. Codex MCP documentation.

Claude Code

Run this in a terminal to add Invoicer for your user account.

claude mcp add --transport stdio --scope user invoicer -- npx -y @invoicer/cli@2.4.0 mcp

Restart Claude Code, run /mcp to check the connection, then ask it to show your clients. Claude Code MCP documentation.

Claude Desktop

Open Claude Desktop → Settings → Developer → Edit Config. Add the Invoicer entry to claude_desktop_config.json.

{
  "mcpServers": {
    "invoicer": {
      "command": "npx",
      "args": [
        "-y",
        "@invoicer/cli@2.4.0",
        "mcp"
      ]
    }
  }
}

On macOS the file is in ~/Library/Application Support/Claude/. On Windows it is in %APPDATA%\Claude\. Quit and reopen Claude, then check its available tools. Local server setup guide.

Cursor

Add this to ~/.cursor/mcp.json for your user account, or .cursor/mcp.json in a project.

{
  "mcpServers": {
    "invoicer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@invoicer/cli@2.4.0",
        "mcp"
      ]
    }
  }
}

Open Cursor’s MCP settings, enable Invoicer and check its tools in Agent. Keep the client on the same computer as your Invoicer workspace. Cursor MCP documentation.

VS Code / GitHub Copilot

Open a local project. From the Command Palette, run MCP: Add Server, select Command (stdio) and enter this command. Name it invoicer and choose a user or workspace destination.

npx -y @invoicer/cli@2.4.0 mcp

Use a workspace config file instead

Add this to .vscode/mcp.json. This VS Code format uses servers as its top-level key.

{
  "servers": {
    "invoicer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@invoicer/cli@2.4.0",
        "mcp"
      ]
    }
  }
}

Start Invoicer from MCP settings, review the trust prompt and enable its tools for your agent session. VS Code MCP documentation.

Other local MCP clients

Choose a local stdio server in your client. Use these values, or the absolute desktop launcher command copied from Invoicer.

Name: invoicer
Transport: stdio
Command: npx
Arguments: ["-y","@invoicer/cli@2.4.0","mcp"]

The client starts the server process. Use its own configuration format; JSON keys and file locations differ between apps.

Connection help

Command not found: your assistant may have a different PATH from your terminal. Use the absolute launcher path from Invoicer → Settings → Integrations, or the full path to npx.
First connection times out: run the CLI version check above once so npm downloads it, then restart the connection. Allow up to 60 seconds for startup if your client supports a timeout setting.
Windows cannot launch npx: use cmd as the command and the arguments below.

["/c","npx","-y","@invoicer/cli@2.4.0","mcp"]

Different workspace or missing records? Select the correct workspace in Invoicer, stop the MCP server and start it again. Each connection keeps the workspace it started with. Run local clients on the same computer; a remote container cannot read your desktop files.

Connected but no tool calls? Check that Invoicer tools are enabled in the client and review its approval prompts. Start by asking it to use Invoicer to show your clients.

Try it with your work

“Use Invoicer to show my clients and this month’s unbilled work.”
“Log 30 minutes for Acme on the landing page update.”
“Preview an invoice for Acme’s unbilled hours, then let me review it.”

You can also control a timer, save a reviewed invoice as an unscheduled draft and export a PDF when your client supports PDF resources. Sending email, deleting records and taking payments are unavailable through these tools.

Your data and permissions

Requested business data is shared with the AI provider you choose. Email credentials and local file paths are excluded from normal tool results. Your MCP client controls tool approvals; local tools use your workspace permissions. Read the privacy policy.

A repeated write uses the same request ID to avoid a duplicate. If an interrupted write has an uncertain outcome, review it in Invoicer before trying again.

Claude and ChatGPT on the web

This setup connects local desktop and terminal clients. A browser connector needs a public HTTPS relay; no Invoicer-hosted relay is currently available. You can use the local connection now without waiting for a directory listing.

Need help?

Contact support@inbrief.sh with your operating system, Invoicer version, MCP client and error message. Leave out credentials and private invoice data.