Connect your AI assistant

MCP (Model Context Protocol) is a standard way to let an AI assistant use a real application on your behalf, so instead of you clicking through the admin, you can just ask.

Behio runs its own MCP server with 1023 tools, which is nearly everything you can do in the admin: warehouse items and stock, e-shop products, orders and shipping, invoices and expenses, contacts and the CRM, marketing, analytics and organization settings. This page shows how to connect it.

The server address is always:

https://be.behio.com/mcp

That is the Behio backend, not the address of the admin you have open in the browser. If you copy app.behio.com into an AI client, the connection will fail.

Connect from Claude

Claude web and desktop app (the button, no config file)

1. Open claude.ai, go to Settings, then Connectors.
2. Click Add custom connector.
3. Name it Behio and paste the server URL: https://be.behio.com/mcp
4. Confirm. Claude sends you to Behio, where you sign in (if you are not signed in already) and see a screen listing what the assistant will be able to do.
5. Click Allow. You land back in Claude and the connector is ready.

There is nothing to copy, no key to store. Claude gets its own access, which expires on its own and renews quietly in the background as long as the connection is live.

Claude Code (terminal)

claude mcp add --transport http behio https://be.behio.com/mcp

Then run /mcp inside Claude Code and pick Authenticate. The browser opens the same approval screen as above.

Claude Desktop by hand (config file)

If you prefer editing the config yourself, add the server to claude_desktop_config.json:

{
  "mcpServers": {
    "behio": {
      "url": "https://be.behio.com/mcp"
    }
  }
}

Restart Claude Desktop. On the first call it opens the Behio approval screen in your browser.

Connect from ChatGPT

Custom connectors need a ChatGPT Plus, Pro, Business or Enterprise plan.

1. In ChatGPT open Settings, then Connectors.
2. Choose Create (or Add custom connector).
3. Name it Behio and paste https://be.behio.com/mcp as the MCP server URL.
4. Pick OAuth as the authentication method and confirm.
5. ChatGPT sends you to Behio to sign in and approve the connection.

After that, start a chat, turn the Behio connector on, and ask it something like "list my organizations" to check that it answers.

Connect from any other client

Two ways in, pick whichever your client supports.

OAuth (recommended). Behio publishes standard discovery documents, so a compliant client only needs the server URL. It finds the rest by itself, including registering itself as a client:

https://be.behio.com/.well-known/oauth-authorization-server
https://be.behio.com/.well-known/oauth-protected-resource

Access key in a header. For clients that do not do OAuth (scripts, self hosted agents, automation tools), send your personal access key in the X-MCP-Token header on every request:

{
  "mcpServers": {
    "behio": {
      "url": "https://be.behio.com/mcp",
      "headers": {
        "X-MCP-Token": "your-access-key"
      }
    }
  }
}

The next section is how you get that key.

Create an access key

1. In the Behio admin, open the AI and MCP module.
2. Go to Access keys and click the button to create one.
3. Name it after the place it will live, for example "Claude on my laptop" or "n8n automation". The name is the only way to tell keys apart later.
4. Optionally set an expiry date. No date means the key works until you delete it.

The key is shown exactly once, right after you create it. Copy it straight into the client that will use it. Behio stores only a fingerprint of the key, so nobody, including us, can read it back to you afterwards. Lose it and you simply delete the key and make a new one. In the list you will only ever see the first eight characters, enough to recognize which key is which.

Treat a key like a password. Anyone holding it can do everything you can do.

What the assistant can actually see

An assistant connected to Behio acts as you, with your permissions, and never more:

• It sees every organization you are a member of, and nothing from organizations you are not in.
• Inside an organization, your role decides the rest. If your role does not give you invoicing, the assistant cannot read or write invoices either, no matter how it is asked.
• Every tool call is checked at the moment it runs, not just when you connect. Change someone's role and their assistant loses that access on the next call.
• Calls are recorded, so you can open a connection or a key in the admin and see which tools ran, when, and whether they succeeded. History is kept for 90 days.

Revoke a connection or a key

Both live in the AI and MCP module in the admin.

• Connection (Claude, ChatGPT, anything that connected through the approval screen): open Connection and revoke it. Access stops immediately and the client cannot renew itself, it has to ask you for approval again.
• Access key: open Access keys and delete it. Every client using it stops working at once.

Revoking keeps the call history, so the record of what was done does not disappear along with the access.