MCP server for bexio

What is an MCP server for bexio?

bexio holds the figures that run your business — open items, project hours, invoices due, QR payment slips — yet anyone who needs a report or an invoice draft still clicks through screens by hand. An MCP server closes exactly this gap. An MCP server for bexio connects AI agents (Claude, GPT, Gemini, Copilot) to your bexio account via the open Model Context Protocol. The model then accesses the bexio API in a standardised way — create invoices, read contacts, analyse projects and time entries — without you having to write custom scripts for every new AI application or patch together a Zapier workaround. We explain separately how MCP differs from classic API function calling.

bexio is well suited for an MCP connection: the API is REST-based, documented and covers the central SME objects — contacts, quotes, invoices, projects, time tracking. That noticeably reduces the effort for the basic integration. We set the timeline after the AI Check.

Community MCP servers with a great many tools already exist on the market, as do connectors via generic automation platforms. These are a good entry point, but often give the AI agent full access to all endpoints. We rely instead on a custom, secured integration into your own agents — limited to your use cases, with clear separation of permissions and EU hosting.

Use cases: what can a bexio MCP server do in practice?

1. Creating invoices by voice “Create an invoice for customer X for the services from project Y.” The agent pulls contact, line items and tax rate from bexio, builds the invoice as a draft — including the Swiss QR bill — and submits it for approval.
2. Preparing dunning The agent checks open items, prioritises by due date and customer value and writes graduated payment reminders as drafts — from a friendly first reminder to a firm dunning notice.
3. Project time analysis “How many hours are booked on project Z and how many of them are billable?” The agent aggregates the time entries from bexio, shows budget utilisation and flags which hours still have to be invoiced.
4. Contact care & master data New contacts from forms or the CRM land cleanly in bexio. The agent checks for duplicates, fills in missing fields and flags when IBAN, UID number or address are incomplete.
5. Quote workflow From a short description, the agent builds a quote in bexio and takes over standard line items and terms — you review once, adjust and send. Accepted quotes can be converted directly into an invoice.
6. Fiduciary handover & reporting Month-end close as a guided routine: open items, revenue by customer, billable project hours. The agent generates a short report — your fiduciary receives clean, prepared figures.

How the integration works

Architecture for bexio:

AI agent ↔ MCP server (your EU host) ↔ bexio API (OAuth 2.0, REST/JSON)

Concrete technical steps:

• OAuth setup: You, as the bexio owner, authorise the MCP server once. Tokens are stored encrypted on the EU host, with a rotation and revoke strategy.
• Tool mapping: We define MCP tools such as create_invoice_draft, list_open_invoices, get_contact and list_timesheets. Each with a JSON schema, validated inputs and clear error messages.
• QR bill: bexio generates the Swiss QR payment slip automatically. The agent supplies only the correct fields — reference, amount, recipient — and leaves QR generation to bexio.
• Read vs. write separation: By default the agent only creates drafts. Publishing, posting or sending requires human approval — configurable per tool.
• Logging: Every API action is logged with timestamp, user and diff — for traceability and audit.

If you want to understand this in more depth, you will find the details in the guide to MCP integration through an agency and in our MCP topic cluster with all tool integrations.

revDSG, hosting & security

According to bexio, bexio runs its servers in Switzerland — a good starting point for Swiss data protection (revDSG, the revised Swiss Data Protection Act). Swiss SMEs are subject to the revised Data Protection Act, and the GDPR additionally applies wherever there are EU touchpoints. To keep the whole system clean, we pay attention to the following with every bexio MCP server:

• Hosting of the MCP server in the EU or Switzerland (e.g. Hetzner, Exoscale, Azure Switzerland) — the obvious choice because bexio itself hosts in Switzerland, which keeps the data chain short and regional.
• Keep bexio OAuth scopes minimal: We authorise the server only for the endpoints your use cases need (such as contacts and invoices), not for the full API permission. The issued tokens are stored encrypted, with a rotation and revoke strategy.
• Data processing agreement with the AI provider in EU data residency (Claude via AWS Bedrock in the EU region Frankfurt, OpenAI Enterprise EU, Azure OpenAI in a Swiss or EU region). Whether a US provider is in the path, we state openly in advance.
• Data minimisation at bexio field level: The server passes personal contact data such as IBAN or UID number to the model only when the specific task absolutely needs it — otherwise it stays in the MCP server.
• Client separation for fiduciaries: If a fiduciary looks after several bexio accounts, each client is run in its own context with its own tokens and roles — the agent can never mix client A’s figures with client B’s.

More on secure setup: MCP server security and GDPR.

What does it cost?

The well-structured API keeps the integration effort for bexio manageable. In concrete terms:

• First use case clearly defined, then step-by-step expansion — typically the invoice workflow or project time analysis as the start.
• Clear scope per use case, no hours roulette. Scaling after that in small, clearly defined steps.

We clarify the exact figure in the free initial conversation — depending on volume (invoices and projects per month), the tools you want and whether multiple accounts are connected.

Frequently asked questions

What does my own bexio MCP server give me compared with a ready-made server?

A ready-made MCP server often gives the agent full access to all bexio endpoints. A custom integration restricts the tools to exactly your use cases, separates read from write permissions and runs on your EU host — targeted permissions instead of a blank cheque. You keep control over what the agent may see and change.

Can an AI agent create a QR bill via bexio?

Yes. bexio automatically generates the Swiss QR bill with a correct QR payment slip. The agent fills in recipient, line items and reference via the API, checks the data and creates the QR bill as a draft — you approve before sending.

Is bexio plus MCP compliant with Swiss data protection (revDSG)?

Yes, if the setup is right: according to its own statements, bexio runs its servers in Switzerland, the MCP server runs in the EU or Switzerland, a data processing agreement with data residency in the EU or Switzerland is in place with the AI provider, and the agent sees only the fields it needs. Which part runs at which provider, we put in writing in advance; the chain can then be operated within the framework of revDSG and GDPR.

Which bexio data can the AI agent use?

In practice these are contacts, quotes and invoices, projects with their time entries and the open items. You determine the scope: every tool gets its own permission from us — from read-only access for reports to write permission for invoice and quote drafts.

How quickly is a bexio MCP integration productive?

We start with a clearly defined use case. We set the timeline after the AI Check. The bexio API is REST-based and well documented, which speeds up the basic integration.