B2Brouter AI Connector (MCP)

The AI Connector lets your usual AI assistant query your B2Brouter account directly, so it answers your questions with real data instead of whatever the AI might imagine.

Instead of going into the web app to search, filter and cross-reference information, you can ask:

"Why did the tax authority reject invoice 2026/0142?" "What do I have pending to collect? What's overdue?" "What channel does this new customer receive invoices on?" "How do I create an invoice via API and send it over Peppol?"

And the assistant looks up the answer in your account and in B2Brouter's official documentation, and explains it to you. You'll find more examples in What you can do.

For technical profiles.

The connector is a remote MCP (Model Context Protocol) server, the open standard for AI assistants to access external data and tools. B2Brouter exposes a set of query tools that any MCP client can discover and invoke. The assistant autonomously decides which tool to invoke based on your question; you just talk.

Before you start

Server URL

https://app.b2brouter.net/mcp

OAuth 2.1 · Streamable HTTP · Remote

The same URL for every client. Nothing to install and no API key to request.

Read-only

The assistant can query invoices, tax reports, figures and the directory. It cannot create, modify, send or delete anything: correcting an invoice, sending it or chasing a payment is up to you, in the web app or via the API. See Why it's read-only.

Requirements

• A B2Brouter account with an active paid subscription. The connector isn't available on the free plan. Invoice, tax report and financial summary features additionally require the Professional plan or higher on the account being queried.
• Your B2Brouter username and password. The connection is made with your personal user.
• An AI assistant compatible with remote MCP connectors: Claude, ChatGPT, Cursor, VS Code or any other MCP client.

Connect it

Choose the assistant you use. In every case, connecting it opens a B2Brouter window in your browser: sign in (if you're not already) and authorize access. You only need to do this once per assistant.

Claude

B2Brouter has its own connector in Claude's connectors directory:

1. Sign in to Claude and open the B2Brouter listing: claude.ai/directory/b2brouter.
2. Click Connect.
3. Sign in to B2Brouter and authorize Claude's access.

It's then available on the web, in the desktop app and on mobile. On Claude Team or Enterprise, an organization owner has to add it first.

In Claude Code, register it as a remote server and then run /mcp to authorize it:

claude mcp add --transport http b2brouter https://app.b2brouter.net/mcp

The full step-by-step guide, including tool permissions and team setup, is in B2Brouter connector for Claude.

ChatGPT

In ChatGPT, the connector is added as a custom MCP server from the web version (chatgpt.com):

1. Open ChatGPT's apps or plugins section, click + and choose Add custom MCP server.
2. Give it a name (for example, "B2Brouter") and paste the server URL: https://app.b2brouter.net/mcp.
3. For authentication, choose OAuth. You don't need to enter a client ID.
4. Accept the warning and create it. The B2Brouter window will open: sign in and authorize access.
5. In a conversation, invoke it by typing @ and choosing B2Brouter.

Note

In Business, Enterprise or Edu workspaces, only admins may be able to add custom MCP servers. If you don't see the option, ask your workspace admin. Menu names may vary depending on your ChatGPT plan and version.

Cursor

Add the server to Cursor's MCP configuration file: ~/.cursor/mcp.json (for all projects) or .cursor/mcp.json (for the current project only):

{
  "mcpServers": {
    "b2brouter": {
      "url": "https://app.b2brouter.net/mcp"
    }
  }
}

Then, in Cursor Settings → Tools & MCP, the server shows up as pending authentication: click it to open the B2Brouter window, sign in and authorize access.

VS Code

With GitHub Copilot in agent mode:

1. Open the command palette and run MCP: Add Server.
2. Choose HTTP, paste the URL https://app.b2brouter.net/mcp and give it an ID (for example, b2brouter).
3. On the first connection, VS Code opens your browser: sign in to B2Brouter and authorize access.

You can also add it by hand to the project's .vscode/mcp.json file:

{
  "servers": {
    "b2brouter": {
      "type": "http",
      "url": "https://app.b2brouter.net/mcp"
    }
  }
}

Note

With Copilot Business or Enterprise licenses, your organization's admin must have the MCP servers in Copilot policy enabled.

Other MCP clients

Any client that lets you add remote MCP servers connects with the same details:

• Server URL: https://app.b2brouter.net/mcp
• Transport: Streamable HTTP (sometimes just called "HTTP").
• Authentication: OAuth. Leave the client ID and secret blank: the client registers itself automatically.

When you add it, the authorization flow opens in the browser: you sign in to B2Brouter and authorize, as in the other cases.

For technical profiles.

Authorization is OAuth 2.1 with Authorization Code + PKCE. MCP clients can self-register (Dynamic Client Registration, RFC 7591), so there's no need to request client credentials from B2Brouter: any standard-compliant client works directly. The resulting token acts on behalf of your user; there are no service tokens or credentials of the assistant's own on the account. The paid subscription requirement is checked on every request: if the subscription expires, access is cut off immediately even if the token is still alive.

Check that it works

Ask a question about your account. The assistant will tell you in the conversation that it's querying B2Brouter:

• "What B2Brouter accounts do I have?"
• "List my invoices with errors from this month"

If it answers with your accounts and your invoices, you're all set. If not, see If something isn't working.

The assistant is you

The assistant acts with your identity and your permissions, no more, no less:

• It only sees the accounts where your user is a member.
• Within each account, it only sees the sections you have permission for. If your access to the company account is limited to received invoices, the assistant won't see issued ones either.
• Each person in the company connects with their own user: access and permissions are never shared.

How it works and security explains this model in detail.

Disconnecting it and seeing what it has done

• Disconnecting it: from your B2Brouter profile → Authorized applications, you can revoke the assistant's access whenever you want. The effect is immediate. You can also remove the connector from the assistant itself.
• Seeing what it has done: every query the assistant makes to your account is logged. On your B2Brouter profile → MCP Activity you'll see what was queried and when, with which function and from which application. If you're an advisor, it also gives you traceability for your clients.

Learn more

What you can do Example questions about invoices, tax reports, figures and the directory.

Tools reference Every connector function, with its parameters and requirements.

How it works and security Identity, read-only access, third-party content and audit.

Limits, troubleshooting and FAQ What it doesn't do, usage limits, connection errors and common questions.