Skip to main content
The Model Context Protocol (MCP) is an open standard that lets AI assistants use external services. The e-invoice.be MCP server gives AI agents access to your invoices, credit notes, Peppol network data and usage statistics.
All MCP tools are read-only. An MCP client cannot create, change or delete data. To create or send documents, use the API reference. To create or send documents from a terminal, or from an AI agent that can run shell commands, use the peppol CLI.

Prerequisites

Before you set up MCP, you need:
  1. An e-invoice.be account. Sign up at app.e-invoice.be.
  2. The API key of your company. Open API settings in the app and copy the key. See Authentication.
The server URL is https://api.e-invoice.be/mcp. It is the same for all clients. The transport is streamable HTTP, and you authenticate with your API key as a Bearer token. The server does not check the API key when the client connects or lists the tools. The API checks the key at each tool call. Thus a client with a wrong key can connect and show the tools, but each tool call that needs a key gives HTTP 401.

Setup

Claude Code supports remote MCP servers with streamable HTTP.Use the command line (recommended):
This command registers the server at local scope: only you can use it, and only in the current project. To use it in all your projects, add --scope user. To share it with your team through the repository, add --scope project. Project scope writes the server to the file .mcp.json in the project root. Do not commit a real API key in .mcp.json.As an alternative, add this JSON to .mcp.json in the project root (project scope):
Then restart Claude Code or run /mcp and make sure that the server is in the list.

Claude Code MCP docs

Official documentation for MCP in Claude Code
If you have no API key, see Authentication.

Available tools

Documents

Inbox

Outbox

Drafts

Peppol lookup

These tools are public and need no authentication.

Statistics

Example prompts

When the client is connected, you can ask questions about your company in natural language:
  • “Show me all invoices received this month”
  • “Get the details and timeline of document doc-1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d”
  • “Is the company with VAT number BE0848934496 registered on Peppol?”
  • “Search for Peppol participants named ‘OpenPeppol’ in Belgium”
  • “Show my send and receive statistics for the last 3 months, by month”
  • “List all failed documents in my drafts”
  • “What attachments are on invoice doc-1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d?”

Troubleshooting

  1. Restart the application. Most MCP clients load the server configuration only when they start.
  2. Make sure that the server URL is https://api.e-invoice.be/mcp, with no slash at the end.
  3. Make sure that the configuration file is valid JSON.
A wrong API key does not prevent the tools from showing. See Authentication errors below.
  • Look for errors in the log file:
    • macOS: tail -n 50 ~/Library/Logs/Claude/mcp.log
    • Windows: open %APPDATA%\Claude\logs\mcp.log
  • Make sure that Node.js 18 or later is installed and on your PATH: node --version.
  • Run mcp-remote manually to see authentication errors:
  • Make sure that the JSON is valid. If the file has a comma at the end of a list or a missing quotation mark, Claude Desktop does not load the server and shows no error.
  • Custom connectors need Developer mode. Enable it in Settings → Connectors → Advanced.
  • Developer mode is not available on all plans and in all regions. Limits can apply in the EEA, the United Kingdom and Switzerland.
  • Enable the connector in each new chat with the + → Connectors menu.
A wrong or absent API key gives HTTP 401 at the tool call, not when the client connects.
  • Make sure that your API key is correct. This request must return your company data:
  • Make sure that you copied the full API key. A company API key starts with api-.
  • An organisation API key for the Admin API does not work with MCP. Use the API key of a company.
  • If you reset your key, update the configuration file and restart the client.
  • For the HTTP status codes of the API, see Errors and troubleshooting.

Security

Your API key gives an MCP client access to all data of your company that the read-only tools can return. Protect it as you protect all API credentials.
  • Read-only access: MCP tools cannot create, change or delete data.
  • Company scope: the API key controls which company the tools can read. An API key belongs to one company.
  • Public lookup tools: get_lookup_peppol_id and get_lookup_participants operate without authentication.
  • Sandbox company first: use the API key of a sandbox company while you try MCP. See Test mode and sandbox companies.

Next Steps

Authentication

Get your API key and learn how the API authenticates requests

API reference

Create and send documents with the REST API

peppol CLI

Create, validate and send documents from a terminal or a script

Webhooks

Receive a notification for each document event