Connect Claude or ChatGPT (MCP connector)

Add Bilify as a custom connector in Claude, ChatGPT or another MCP client, choose the workspace, see what the assistant can do and revoke access.

4 min read Updated 04.10.2026 Requires: AI assistant connector (MCP)

Bilify has a built-in MCP server (Model Context Protocol), so an AI assistant such as Claude or ChatGPT can work with your invoices, clients, items, expenses, contracts and statistics in a normal conversation: "Which invoices are overdue?", "Draft an invoice for Alfa Trade for 10 hours of consulting". There is nothing to install or host. The assistant signs in with your Bilify account and can only do what your role allows.

What you need

  • A package that includes the AI connector. If it does not, Settings > Integrations shows Upgrade to connect AI assistants.
  • An active subscription for the workspace.
  • An assistant that supports custom (remote) MCP connectors with OAuth sign-in. Claude and ChatGPT both do on plans that allow custom connectors; other MCP clients work the same way.

1. Copy the MCP endpoint

  1. In Bilify, open Settings > Integrations.
  2. In Connect an AI assistant, copy the MCP endpoint. It is your Bilify address followed by /mcp.

Only owners and admins see the Integrations page. Anyone else in the team can ask them for the address; it is the same for everyone.

2. Add the connector in your assistant

The exact menu names belong to the assistant's vendor and change from time to time, so follow their current help if a label below differs.

Claude. Open Claude's settings and find the connectors section, then choose to add a custom connector. Give it a name (for example "Bilify") and paste the MCP endpoint as the URL. On team plans an owner may have to add the connector for the organisation first.

ChatGPT. Open ChatGPT's settings and look for connectors (apps). Adding your own MCP server may require a developer mode or an admin, depending on your plan. Create a new connector, paste the MCP endpoint as the server URL and choose OAuth as the authentication.

Other MCP clients. Add a remote (HTTP) MCP server with the endpoint URL. The client discovers Bilify's OAuth settings and registers itself automatically.

3. Sign in and choose the workspace

When the assistant connects for the first time, a Bilify window opens:

  1. Sign in with your Bilify account if you are not signed in already.
  2. On Authorize connection, check the Signed in as line.
  3. Under Workspace to connect, choose the company the assistant may work in. One connection is tied to one workspace. To connect another workspace, authorize again and pick that one.
  4. Click Authorize (or Cancel to stop).

Pick your production workspace

The AI connector always works with real (production) data. If you have enabled the sandbox, your workspace may appear twice in the list with the same name. Choose the real one; a connection to the sandbox is refused when the assistant tries to use it. To test against sandbox data, use the REST API with a blf_test_ key instead.

The connection then appears under Active connections in Settings > Integrations.

What the assistant can do

The connector offers 29 tools:

Area Tools
Documents (7) list documents, get a document, create a draft, update a draft, issue a document, record a payment, delete a draft
Clients (4) list, get, create, update
Items (4) list, get, create, update
Expenses (5) list, get, create, update, delete
Statistics (4) business summary, outstanding receivables, top clients, monthly trends
Contracts (5) list, get, create a draft contract, send a contract for signature, void a contract

Things to know:

  • Your permissions apply. Every tool checks your role in the chosen workspace. If you cannot issue documents in the app, the assistant cannot either. If you are removed from the workspace, the connection stops working at once.
  • Drafts first. Documents and contracts are always created as drafts. Issuing a document (which assigns the number and makes it final) and sending a contract are separate tools that the assistant is told to use only after you confirm.
  • Signing is not done by the assistant. Signers sign through the email link, as with any contract.
  • Everything is logged. Each change appears in the activity log under your name, like a change you made yourself in the app.
  • Limits. Each connection can make up to 60 requests per minute. Package limits (documents per month, clients and so on) apply as in the app.

Ask clearly, then check

Give the assistant the client name, amounts and dates. Before you let it issue an invoice, ask it to show you the draft, or open the draft in Bilify.

See and revoke connections

Settings > Integrations > Active connections lists every connection to this workspace with Connector, Authorized by, Connected, Last used and Environment. Last used currently always shows Not yet used, because Bilify does not record usage of connections yet.

To cut off an assistant:

  1. Click Revoke in its row.
  2. Confirm. The assistant loses access to this workspace immediately.

Revoking needs the integrations management permission (owners and admins). Team members without it can remove the connector in their assistant's settings, or ask an owner or admin to revoke it here. To connect again later, simply use the connector in the assistant and authorize once more.

Was this page helpful?

Related articles

API keys Create, roll and revoke the keys your scripts use to call the Bilify REST API, for production or for the sandbox. Sandbox mode A separate test copy of your workspace with its own data, test API keys and webhooks, where emails are never sent and e-Faktura runs in the simulator. Roles and permissions What the Owner, Admin, Accountant and Employee roles can do in Bilify, and how to give one person a custom set of permissions. Activity log See who did what and when in your workspace, from issued invoices to portal logins, and filter the history by person, subject, type and date.

Still stuck?

Write to us and we will get back to you within one working day.

Contact us