Connect your AI assistant

Server details


Endpoint	`https://connect.neetoinvoice.com/mcp/messages`
Transport	HTTP
Authentication	OAuth, or `Authorization: Bearer <your-api-key>`

Which method does my client use?

The credential decides the permissions boundary, so read Authentication before picking.

Client	OAuth	API key
Claude (claude.ai, desktop)	Yes	-
ChatGPT	Yes	-
Claude Code	Not yet	Yes
Codex	Not yet	Yes
Cursor	Not yet	Yes
Gemini CLI	Not yet	Yes
VS Code	Not yet	Yes
Windsurf	Not yet	Yes

Terminal and editor clients register a http://localhost/... callback during OAuth. This deployment currently accepts only HTTPS callbacks, so those clients use an API key for now. Claude and ChatGPT redirect over HTTPS and work with OAuth today.

OAuth clients

Claude
ChatGPT

Open Settings → Connectors.
Click Add, then Add custom connector.
Enter a Name, for example NeetoInvoice.

Paste the URL:

https://connect.neetoinvoice.com/mcp/messages

Click Add, then Connect and approve the workspace in the browser window.

Works on claude.ai and the Claude desktop app.

Open Settings → Security and login and turn on Developer mode.
Go to Plugins → Browse plugins → + and choose New Plugin.

Paste the URL:

https://connect.neetoinvoice.com/mcp/messages

Approve the workspace in the browser window.

API key clients

Replace YOUR_API_KEY in every block with a key from your workspace. See Authentication.

claude mcp add --transport http neeto-invoice \
  https://connect.neetoinvoice.com/mcp/messages \
  --header "Authorization: Bearer YOUR_API_KEY"

Or add it to ~/.claude.json by hand:

~/.claude.json

{
  "mcpServers": {
    "neeto-invoice": {
      "type": "http",
      "url": "https://connect.neetoinvoice.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Save and restart Claude Code.

Codex uses TOML, not JSON. Add to ~/.codex/config.toml:

~/.codex/config.toml

[mcp_servers.neeto-invoice]
url = "https://connect.neetoinvoice.com/mcp/messages"
bearer_token_env_var = "NEETOINVOICE_API_KEY"

bearer_token_env_var is the name of the environment variable, not the key itself. Export the key in your shell:

export NEETOINVOICE_API_KEY=YOUR_API_KEY

Add the server to ~/.cursor/mcp.json:

~/.cursor/mcp.json

{
  "mcpServers": {
    "neeto-invoice": {
      "url": "https://connect.neetoinvoice.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Save, then restart Cursor or reload the window.

Add the server to ~/.gemini/settings.json. Gemini CLI names the field httpUrl; plain url means SSE and will not work here:

~/.gemini/settings.json

{
  "mcpServers": {
    "neeto-invoice": {
      "httpUrl": "https://connect.neetoinvoice.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Add the server to .vscode/mcp.json in your workspace. VS Code nests servers under servers, not mcpServers:

.vscode/mcp.json

{
  "servers": {
    "neeto-invoice": {
      "type": "http",
      "url": "https://connect.neetoinvoice.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Requires VS Code 1.99 or later, with GitHub Copilot Chat in Agent mode.

Unlike the other clients, this config lives inside your repository. Add .vscode/mcp.json to .gitignore before you paste a key into it, or you will commit a working API key.

Add the server to ~/.codeium/windsurf/mcp_config.json. Windsurf names the field serverUrl, not url:

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "neeto-invoice": {
      "serverUrl": "https://connect.neetoinvoice.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Save, then enable the server under Settings → Cascade → MCP Servers. Windsurf caps the number of MCP tools it loads across all servers, so disable servers you are not using.

Three keys differ between clients and cause most silent failures: VS Code nests under servers while the others use mcpServers; Windsurf names the endpoint serverUrl and Gemini CLI names it httpUrl, while the others use url; and Codex uses TOML rather than JSON.

Confirm the connection

Ask your assistant to list your workspaces. It should call ListWorkspaces and report the workspace your credential belongs to.

List my NeetoInvoice workspaces

If nothing happens, see Troubleshooting.

Next steps

Examples

Prompts to try once the connection is live.

Tools

Every tool the server exposes.

Getting Started

Reference

Server details

Which method does my client use?

OAuth clients

API key clients

Confirm the connection

Next steps

Examples

Tools

​Server details

​Which method does my client use?

​OAuth clients

​API key clients

​Confirm the connection

​Next steps

Examples

Tools

Server details

Which method does my client use?

OAuth clients

API key clients

Confirm the connection

Next steps