bexio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_HOST | No | Bind host in HTTP mode | 0.0.0.0 |
| MCP_HTTP_PORT | No | Port in HTTP mode | 3000 |
| MCP_TRANSPORT | No | stdio or http | stdio |
| MCP_HTTP_TOKEN | No | If set: required bearer token for /mcp | |
| BEXIO_API_TOKEN | Yes | bexio PAT or OAuth2 access token | |
| BEXIO_API_BASE_URL | No | API base URL | https://api.bexio.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bexio_list_contactsB | List contacts from bexio (GET /2.0/contact). Supports pagination and ordering. |
| bexio_get_contactB | Fetch a single contact by id (GET /2.0/contact/{id}). |
| bexio_search_contactsB | Search contacts with field criteria (POST /2.0/contact/search). |
| bexio_list_invoicesB | List invoices from bexio (GET /2.0/kb_invoice). Supports pagination and ordering. |
| bexio_get_invoiceB | Fetch a single invoice by id (GET /2.0/kb_invoice/{id}). |
| bexio_search_invoicesC | Search invoices with field criteria (POST /2.0/kb_invoice/search). |
| bexio_list_quotesB | List quotes / offers from bexio (GET /2.0/kb_offer). Supports pagination and ordering. |
| bexio_get_quoteA | Fetch a single quote by id (GET /2.0/kb_offer/{id}). |
| bexio_search_quotesC | Search quotes / offers with field criteria (POST /2.0/kb_offer/search). |
| bexio_list_ordersA | List orders from bexio (GET /2.0/kb_order). Supports pagination and ordering. |
| bexio_get_orderB | Fetch a single order by id (GET /2.0/kb_order/{id}). |
| bexio_search_ordersC | Search orders with field criteria (POST /2.0/kb_order/search). |
| bexio_list_itemsA | List items / articles from bexio (GET /2.0/article). Supports pagination and ordering. |
| bexio_get_itemB | Fetch a single item by id (GET /2.0/article/{id}). |
| bexio_search_itemsB | Search items / articles with field criteria (POST /2.0/article/search). |
| bexio_list_projectsA | List projects from bexio (GET /2.0/pr_project). Supports pagination and ordering. |
| bexio_get_projectA | Fetch a single project by id (GET /2.0/pr_project/{id}). |
| bexio_search_projectsC | Search projects with field criteria (POST /2.0/pr_project/search). |
| bexio_get_company_profileA | Fetch the bexio company profile(s) of the authenticated account (GET /2.0/company_profile). |
| bexio_create_contactB | Create a contact in bexio (POST /2.0/contact). contact_type_id 1 = company, 2 = person. For a person, set name_1 = last name and name_2 = first name. |
| bexio_requestA | Make an arbitrary authenticated request to the bexio API. Use this for any endpoint not covered by a dedicated tool (e.g. /3.0/banking/accounts, /2.0/user, /2.0/taxes, /2.0/kb_invoice/{id}/payment). See https://docs.bexio.com/ for the full reference. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Each tool targets a distinct resource-action pair (e.g., list vs. search vs. get for contacts, invoices, etc.), with no overlap. The generic request tool covers any missing endpoints, further reducing ambiguity.
All tools follow a consistent 'bexio_<verb>_<resource>' pattern in snake_case, with verbs like create, get, list, search, and request. Naming is predictable and uniform.
21 tools cover the main business objects (contacts, invoices, items, orders, projects, quotes) plus a generic request endpoint. This is well-scoped for an ERP system, avoiding fragmentation or sparseness.
Only create_contact exists; there are no create, update, or delete tools for invoices, orders, projects, quotes, or items. Agents can only read and search these resources, which severely limits workflows without the generic request tool.