Frihet MCP Server: AI Connected to Business Management

An MCP server lets an artificial intelligence client work with external tools through a shared contract. In Frihet, that contract provides another way to query information and prepare operations. It does not replace the API, the ERP interface, or the controls applied by the account owner.

The practical model is straightforward: the client interprets a request, selects a server tool, and presents its arguments. Frihet processes the operation with the configured account and credentials. The convenience of a conversational interface therefore needs the same discipline as any integration that handles business data.

What Frihet publishes

Frihet’s product manifest records a live MCP server at version 1.16.6, verified on 28 August 2026. Its current contract contains 157 tools across 17 families, 11 resources, and 10 prompts. It is available as an npm package and a remote endpoint, and its source is published under the MIT license.

The families cover clients, invoices, expenses, deposits, products, quotes, webhooks, CRM, electronic invoicing, banking, fiscal models, VeriFactu, TicketBAI, time entries, and recurring invoices. This list describes server surfaces. It does not mean every request should run without validation.

Frihet also maintains a documented REST API with API-key authentication and a webhook system with 94 event types and HMAC-SHA256 verification. MCP uses that programmatic foundation and adds a standardized way to discover tools and pass arguments to them.

Read before you write

A good first MCP workflow starts with read operations. You might list recent invoices, inspect expenses for a period, or find a client. The MCP client should expose the selected tool and parameters so you can confirm that the planned request matches your intent.

Write operations need more care. Creating or updating an invoice changes accounting data; editing a client affects information that may be reused in later documents. Before confirming a sensitive action, review at least:

• the Frihet account and environment in use;
• the selected client and resource identifiers;
• currency, amounts, dates, and tax fields;
• the exact tool and arguments to be sent;
• the response returned by the API.

MCP makes interaction easier, but it cannot turn an ambiguous instruction into a correct fiscal decision. When an operation has accounting or regulatory consequences, review the draft and use the approval process established by your business.

Local package and remote endpoint

The local package is distributed as @frihet/mcp-server. Exact configuration depends on the MCP client, but the usual pattern is to register the server command and provide the API key through a protected environment variable.

Frihet also publishes the remote endpoint at https://mcp.frihet.io/mcp. This mode avoids running a local process, while still requiring authentication and a deliberate choice about which client receives access.

Never paste an API key into a conversation, shared document, or repository. Use the environment’s secret mechanism, keep credentials separate when working with different accounts, and revoke credentials that are no longer required.

Three useful starting workflows

1. Prepare an invoice operation

You can provide a client, description, amount, and date to prepare the relevant operation. Before creating the record, check fiscal data, numbering, and any calculated fields. The goal is to reduce navigation and transcription, not to remove review.

2. Inspect outstanding invoices

A read query can retrieve invoices by state or due date. You can use the result to decide which items need follow-up and draft communications separately. Sending a message should remain subject to the configuration and approvals in your workflow.

3. Query activity from a working environment

A technical team can inspect clients, products, or invoices from an MCP client without switching context. Credentials should still be limited to the correct environment, and the response should be checked against the expected account.

MCP, APIs, and webhooks have different jobs

The API provides endpoints for programmatic integrations. Webhooks announce events so another system can react. MCP lets a compatible client discover tools and call them through a common protocol. The three mechanisms can work together, but they are not interchangeable.

For deterministic and repeatable workflows, a direct API integration or webhook is often the appropriate foundation. For exploring data, preparing an operation, or working from a conversational interface, MCP can reduce friction. Authentication, input validation, and result logging remain essential in both cases.

A controlled way to start

1. Read the server documentation and your MCP client’s configuration guide.
2. Create or select an API key for the correct environment.
3. Configure the local package or remote endpoint.
4. Start with a narrow read query.
5. Inspect the selected tool, arguments, and response.
6. Enable write operations only when the review process is clear.

The value of MCP is not a promise that an ERP runs itself. It is an open, inspectable contract that helps people and their tools work with Frihet more directly while retaining control over each change.