Developers · AI
What is the Billnado MCP server?
Use Billnado through MCP: read and write actions, authentication, administration selection with subscriberId and current client tools.
Updated on October 7, 2026
The Billnado MCP server (Model Context Protocol) gives compatible AI clients access to Billnado data, actions and product documentation. You can retrieve information and request supported changes in natural language. Billnado checks your account, access to the selected administration and each action’s requirements.
These guides cover visual chatbots and local use of the Codex app. CLI clients and IDE extensions are outside their scope.
Connection details
| Item | Value |
|---|---|
| Transport | Streamable HTTP |
| Primary endpoint | https://mcp.billnado.be/mcp |
| Alternative endpoint | https://mcp.facturatie-systeem.be/mcp |
| Authentication | OAuth 2.0 with PKCE |
| Tool documentation | mcp.billnado.be/documentation |
| Health check | mcp.billnado.be/health |
Use the primary endpoint for new connections whenever possible. The alternative endpoint provides the same server under the Facturatie Systeem domain.
The server publishes OAuth Protected Resource Metadata. Clients that support OAuth discovery and Dynamic Client Registration can therefore start the sign-in flow automatically. Sign in with your regular Billnado account. Never share a password, access token or refresh token in a prompt or configuration file.
Available capabilities
The current tools, parameters and annotations are listed in the live tool documentation. Capabilities include:
| Subject | Capabilities |
|---|---|
| Administrations | Find accessible administrations, retrieve the active administration and, on request, establish an available accountant or support connection. |
| Relations and products | Search and retrieve data, create and change it, and perform supported archive actions. |
| Sales and purchase documents | Search, retrieve, create, change and confirm documents; perform supported copy, conversion, payment and export actions. |
| Financial follow-up | Record payments, reconcile outstanding amounts and retrieve available bank, cash flow and cashbook information. |
| Projects and settings | Manage supported project data, administration settings and other areas using the tools offered by your client. |
| Licences | Retrieve definitions and current or historical licences, and calculate a plan change price. Purchase or change licences and manage automatic renewal in My licence; MCP licence tools are read-only. |
| Documentation | Search languages and articles, retrieve full articles and request contextual page help. |
The server offers both read and write actions. A write action can create, change or delete data, or initiate an actual email, Peppol delivery or accounting operation. Available actions also depend on your rights, licence and client settings.
Important: check the administration, document, data and consequences before a write action. Recording a payment or reconciling an amount records financial processing; it does not execute a bank transfer. Email and Peppol delivery do have an external recipient.
Working with administrations
Without subscriberId, an administration-scoped tool uses your account’s default administration, or otherwise its first accessible administration. To use another administration:
- Have
subscribers_listfind accessible administrations and the access route. - Select the intended administration. Only explicitly request
subscriber_connectto establish an accountant or support connection when one is still needed. - Have the client pass the selected ID as the optional
subscriberIdparameter on every subsequent administration-scoped tool call.
No SubscriberId HTTP header or reconnection is needed. The selection applies per call and does not change your account’s default administration. The client must keep passing the parameter for follow-up questions. Billnado verifies an active access connection; finding an ID does not grant access. Account-wide and general tools do not use this administration parameter.
Guidelines for visual chatbots
- Search before retrieving details: for example, use
relations_searchbeforerelations_getanddocumentation_searchbeforedocumentation_get. - Ask the user to confirm the administration when more than one result is possible.
- Treat tool results as financial and personal data. Include only necessary information in prompts, logs and answers.
- Build integrations around MCP tool names and structured results, not by scraping the public documentation page.
- Recheck tool annotations and parameters when the server changes; the live tool documentation is generated from the same registered tools.
Refresh outdated tools
How new tools become available depends on the client. For a stored tool list, refresh the connector or have an administrator update its actions. Start a new conversation if needed. Signing in again does not refresh approved tool definitions in every client.
ChatGPT workspaces use an approved snapshot: an administrator must refresh and allow changed actions. Microsoft 365 Copilot discovers tools at runtime in the default dynamic configuration; a pinned selection requires a manifest update and republication. Follow the appropriate client guide below.
Example questions
- “Find customer Acme and show its VAT number and primary email address.”
- “Which administrations can I access?”
- “Show the active license and current usage limits.”
- “Search the English Billnado documentation for how to access the API.”
Choose the installation guide for your client:
