Bexio MCP Server

What bexio-mcp-server MCP server does

The bexio-mcp-server MCP server connects MCP-compatible AI clients and workflow systems to Bexio, a Swiss business accounting platform. It provides 314 tools covering common operational areas such as contacts, invoices, quotes, orders, projects, time entries, banking, accounting, purchases, files, and payments.

Agents can use the server to search for records, create and update business data, manage invoice workflows, inspect overdue payments, summarize project time, and work with customer revenue information. The available scope also includes Swiss QR-bill and IBAN payment operations, currency and bank-account management, and optional payroll functions when the Bexio Payroll module is enabled.

How it works

The server communicates with Bexio through the Bexio API and presents those operations as MCP tools. In stdio mode, an MCP client starts the Node-based package locally and passes the API token through its environment. In HTTP mode, the process listens on a local port and exposes MCP over HTTP, allowing n8n or another HTTP-capable MCP client to connect.

A single Bexio API token belongs to one company mandate. To work with several companies, configure one token per company in the same server process. The list_companies and select_company tools allow the active company to be changed during a conversation. Tool registration can also be limited by category to reduce the context required by smaller models or focused workflows.

Setup and configuration

The bexio-mcp-server MCP server requires either BEXIO_API_TOKEN for one company or BEXIO_API_TOKENS for multiple companies. Tokens are created in the Bexio developer portal under Personal Access Tokens. BEXIO_DEFAULT_COMPANY can select the initial company when multiple tokens are configured.

For Claude Desktop, install the .mcpb release bundle through the Extensions settings, or add the npm package to claude_desktop_config.json. A stdio configuration supplies BEXIO_API_TOKEN in the server environment. For HTTP use, start the package with --mode http and a port such as 8000, then point the MCP client at http://localhost:8000.

Optional settings include BEXIO_BASE_URL, which defaults to https://api.bexio.com/2.0, and BEXIO_ENABLED_CATEGORIES, a comma-separated allowlist of tool categories. If the category variable is empty or unset, all categories remain enabled.

Tools and capabilities

Supported areas include:

• Contacts, contact groups, sectors, titles, salutations, and contact relationships
• Invoices, quotes, orders, deliveries, incoming payments, and invoice previews
• Projects, milestones, work packages, timesheets, activities, and communication types
• Banking, QR-bills, IBAN payments, currencies, and bank accounts
• Chart of accounts, journal entries, business years, VAT periods, and account groups
• Bills, expenses, purchase orders, outgoing payments, files, and documents
• Payroll employees, absences, and payroll documents when the required Bexio module is available

The package includes tools for finding contacts, searching projects and timesheets, retrieving overdue invoices, and calculating customer revenue from paid invoices.

Limitations and notes

The project is described as early-release software and may contain bugs or unexpected behavior while development continues. Bexio authentication is mandatory, and each API token is restricted to one company. Payroll-related tools depend on having the Bexio Payroll module.

The server is documented as fully supported with Claude Desktop over stdio and n8n over HTTP. Other MCP clients may work over stdio or HTTP, but the material describes that support as expected rather than fully validated.