Skip to content

Connecting an AI assistant

Consoletium can be added to Claude as a connector, so you can ask questions in Claude and get answers from your own company's data. For example:

  • "Which salesmen sold less this quarter than the same quarter last year?"
  • "What does Acme Pets owe us, and which invoices are overdue?"
  • "Show me last month's P&L next to the month before."

Any other AI assistant that supports MCP connectors (the Model Context Protocol) works the same way, including Claude Desktop and Claude Code.

The connector only reads. Nothing can be posted, changed or deleted through it, whatever the assistant is asked to do.

It is included in every plan and does not use the AI budget under Setup › Plan & Licence. The assistant runs on your own Claude account.

What the assistant can see

The connector signs in with an API key, and every API key acts as one user. So the assistant sees exactly what that user's role allows, and nothing else:

  • If the role has no view rights on payroll, the assistant cannot read payroll.
  • If the role is not allowed the financial reports, the P&L and balance sheet are refused. The assistant is told they were refused, not that they are empty.
  • A sales-rep role sees its own customers only, exactly as on the screens.

The assistant can search; read customers, vendors, items and stock; read orders, invoices, bills, payments and journals; run Sales Analysis; read a customer statement; and run the P&L, balance sheet, trial balance, cash flow, general ledger, AR and AP aging, inventory value, budget against actual, sales by rep and lapsed customers. It can also reach the other read-only lists in the system: warehouse, HR, banking, planning and so on.

Setting it up (once, by an administrator)

  1. Make a role for the assistant: Setup › Roles. Give it View on what it may read. Leave out what it should not see, such as payroll or the financial reports.
  2. Make a user with that role: Setup › Users, for example "Claude assistant". Nobody signs in as this user; it only gives the key its permissions. Administrator users cannot have keys.
  3. Issue a key: Operations › Setup › API Keys, Webhooks & AI Connector. Click New key, choose the user from step 2 under Acts as, and optionally choose when it expires. The key is shown once: copy it now.
  4. Copy the connector address from the AI assistant connector panel on the same screen. It is your company's address followed by /api/mcp, for example https://yourcompany.consoletium.com/api/mcp.

Adding it in Claude

In Claude, go to Settings › Connectors › Add custom connector, then:

Field Value
Name Consoletium (or your company's name)
Remote MCP server URL the connector address from step 4
Authentication No sign in
Request headers name X-API-Key, value: the key from step 3

On Team and Enterprise plans, an owner adds the connector once for everyone. Then each person switches it on in a chat, from the connectors menu.

Other tools can send the key as Authorization: Bearer csk_… instead of X-API-Key. Both work.

Switching it off

Revoke the key on the same screen. The assistant is refused from the next question onwards. The table shows when each key was last used.

For developers

The endpoint is POST /api/mcp. It speaks the MCP Streamable HTTP transport: stateless JSON-RPC 2.0, answered as application/json, with protocol versions 2024-11-05 to 2025-11-25.

  • Each tool is a GET on an existing endpoint, run inside the server with the caller's own key. Permissions, module gates and rate limits therefore apply unchanged.
  • list_read_endpoints and read_endpoint reach every other read endpoint in the API.
  • Answers longer than about 60,000 characters are cut, with a note asking for a smaller limit or a narrower filter.