Use NeetoInvoice in VS Code

Check requirements

• VS Code installed on your computer.
• A NeetoInvoice account.

Connect NeetoInvoice to VS Code

You need VS Code 1.99 or later, with GitHub Copilot in Agent mode. Create .vscode/mcp.json in your workspace. Use servers, not mcpServers. Sign in to NeetoInvoice when VS Code asks.

Then ask in Copilot Chat. VS Code asks before it runs a command, but not before it calls a NeetoInvoice tool:

{
  "servers": {
    "neetoinvoice": {
      "type": "http",
      "url": "https://connect.neetoinvoice.com/mcp/messages"
    }
  }
}

Connect with an API key

An API key is not tied to a person. Every tool call reaches the whole workspace, and role checks do not run. Use a key for automation that must see every time entry. Do not use one on a machine where the person should see only their own entries.

The key is the same one the REST API uses. Learn how to get one in the API keys article. Send it in this header:

Authorization: Bearer YOUR_API_KEY

In Claude Code, Codex, Cursor, Antigravity CLI, VS Code, and Devin, leave the key out of the config to sign in with OAuth. Put the key in to use the API key.

Create .vscode/mcp.json in your workspace. VS Code asks for the key the first time the server is used. Never paste the key into this file, because it lives in your project and can end up in a commit.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "neetoinvoice-api-key",
      "description": "NeetoInvoice API key",
      "password": true
    }
  ],
  "servers": {
    "neetoinvoice": {
      "type": "http",
      "url": "https://connect.neetoinvoice.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer ${input:neetoinvoice-api-key}"
      }
    }
  }
}

VS Code's Copilot agent does not read servers that use ${input:...}. To use the key there, put the server in .mcp.json at the root of your workspace and read the key from an environment variable:

{
  "mcpServers": {
    "neetoinvoice": {
      "type": "http",
      "url": "https://connect.neetoinvoice.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer ${NEETOINVOICE_API_KEY}"
      }
    }
  }
}

Set NEETOINVOICE_API_KEY in the environment that starts VS Code. The sign-in setup above works in both the Local and Copilot agents.

Try these prompts

Clients, projects, and recipients

Get details for client Acme Corp.

Which projects is oliver@example.com on?

Add accounts@example.com as an invoice recipient for Acme Corp.

Invoices

Email the last invoice to Acme Corp's recipients.

Reports, PTO, and team

Show the payroll summary for July 2026.

Show the monthly PTO report for July 2026.

List all active team members.

Work across workspaces

Which NeetoInvoice workspaces can you see?

Troubleshooting

VS Code never offers the tools

MCP needs VS Code 1.99 or later with GitHub Copilot in Agent mode. It is not available in Ask or Edit mode. Confirm that .vscode/mcp.json is in the workspace you have open. With an API key, answer the key prompt the first time the server is used.

Your AI assistant shows no NeetoInvoice tools

Restart the client first. Every client reads its MCP config at startup. On Claude or ChatGPT, confirm that you added the connector and finished the sign-in. In ChatGPT, the plugin is created only after you tick I understand and want to continue.

On Claude Code, Cursor, Codex, VS Code, Devin, Antigravity, or Antigravity CLI, check these:

1. The config key. Claude Code, Cursor, Devin, Antigravity, and Antigravity CLI use mcpServers. VS Code uses servers. Codex uses a [mcp_servers.<name>] section in TOML. A server under the wrong key is ignored silently.
2. The URL key. Antigravity and Antigravity CLI expect serverUrl. Claude Code, Codex, Cursor, Devin, and VS Code expect url.
3. The endpoint. It is https://connect.neetoinvoice.com/mcp/messages, with no trailing slash.
4. The syntax. In JSON, a trailing comma or an unclosed brace makes the whole file unreadable.

The connection is refused or unauthorized

With an API key, the Authorization header must read Bearer YOUR_API_KEY, with the word Bearer and a single space before the key. Confirm the key is not revoked and belongs to the workspace you expect. A key from one workspace does not work in another. With OAuth, remove the connector and add it again to run the sign-in from the start.

More fixes are in the NeetoInvoice MCP troubleshooting guide.

Use NeetoInvoice in other AI assistants

Prefer the terminal? The NeetoInvoice CLI reaches the same data from your shell, your scripts and your coding agent.