Connect an assistant — Finance

Q: The connector URL

Finance exposes an MCP server (Model Context Protocol, the open standard AI assistants use to talk to external systems) at your organization's URL: If you work in a personal space rather than a shared organization: It speaks the standard Streamable HTTP transport, so any compatible client can connect: Claude, ChatGPT, Claude Code, Cursor and more.

Q: Two ways to authenticate

Sign in with your account (OAuth) — recommended This is the path for Claude and ChatGPT. Add the connector URL as a remote connector in the client; the first time you connect, a window opens to sign in with your own account and approve access. From then on the assistant acts as you: it sees what your role lets you see, and only that. There's no key to copy, store or email. Revoking the session or disconnecting the assistant from your account cuts access immediately. An API key For clients that take a token (Cursor, Claude Code, scripts): generate a key under API keys, in your account, and send it in an Authorization: Bearer header. The value is shown once — keep it as safe as any password. A key can be bound to a specific organization or left unbound; without an organization, no tool that needs organization data will work until you bind it from your account.

Q: What the assistant can do

With either path, the assistant can: Read — invoices, estimates, purchases, contacts, dashboard KPIs, a project's financial summary, subscriptions and budget versus actual. Act, with your confirmation — trigger a Holded sync, attribute a document to a project, create a subscription. These three ask for explicit confirmation before actually running: the assistant shows you what it's about to do first. Every call is scoped to your organization and checks the same permission you'd have in the app — if your role can't see the annual budget, the assistant can't see it on your behalf either.

The connector URL

Finance exposes an MCP server (Model Context Protocol, the open standard AI assistants use to talk to external systems) at your organization's URL:

https://<your-organization>.slxd.app/mcp/finance

If you work in a personal space rather than a shared organization:

https://finance.slxd.app/mcp/finance

It speaks the standard Streamable HTTP transport, so any compatible client can connect: Claude, ChatGPT, Claude Code, Cursor and more.

Two ways to authenticate

This is the path for Claude and ChatGPT. Add the connector URL as a remote connector in the client; the first time you connect, a window opens to sign in with your own account and approve access. From then on the assistant acts as you: it sees what your role lets you see, and only that.

There's no key to copy, store or email. Revoking the session or disconnecting the assistant from your account cuts access immediately.

An API key

For clients that take a token (Cursor, Claude Code, scripts): generate a key under API keys, in your account, and send it in an Authorization: Bearer header. The value is shown once — keep it as safe as any password.

A key can be bound to a specific organization or left unbound; without an organization, no tool that needs organization data will work until you bind it from your account.

What the assistant can do

With either path, the assistant can:

Read — invoices, estimates, purchases, contacts, dashboard KPIs, a project's financial summary, subscriptions and budget versus actual.
Act, with your confirmation — trigger a Holded sync, attribute a document to a project, create a subscription. These three ask for explicit confirmation before actually running: the assistant shows you what it's about to do first.

Every call is scoped to your organization and checks the same permission you'd have in the app — if your role can't see the annual budget, the assistant can't see it on your behalf either.

No client handy? Use the panel

The built-in assistant answers over the same tools with nothing to configure — useful for checking a connection works before setting up an external client.