Skip to content

MCP server for AI assistants

Check and create e-invoices with your AI assistant

With the MCP server, AI assistants such as Claude can check and create e-invoices for you: you describe the invoice or attach a file in the chat, and the assistant calls the tools listed below. The server uses the Model Context Protocol (MCP, transport “Streamable HTTP”). You add it to your assistant via its URL and then sign in with your account and allow access, or you use an API key.

Tools

  • validate_e_invoice: checks an e-invoice (XML, or PDF with embedded XML) and returns the errors and warnings with rule ID and a link to the explanation of the rule. The validators used depend on the format: KoSIT and Mustang, the EN 16931 Schematron only for ZUGFeRD / Factur-X. Files are passed Base64-encoded in a request of at most 16 MB, so PDF files can be up to about 12 MB. Counts as a validation of your plan; also available with API access for checking only.
  • explain_validation_rule: explains a validation rule by its rule ID with the published content of our rule pages: meaning, typical causes, how to fix it and, where available, examples of wrong and correct XML. validate_e_invoice includes these explanations for the reported rules where published, so your assistant can explain the errors in plain language and suggest corrections; whether a corrected invoice passes is shown by a new check. Does not count as a validation of your plan; also available with API access for checking only.
  • create_e_invoice: creates a ZUGFeRD PDF/A-3 or, with the profile XRECHNUNG, an XRechnung XML from invoice data with the same fields as POST /api/v1/invoices/. Before the file is created, the invoice is checked against the KoSIT rules; if it does not pass, the assistant receives the validator messages and the invoice is not kept. Created invoices are saved in your account. Requires a plan with full API access.

Who is it for?

  • Self-employed and companies who already work with an AI assistant such as Claude and want to check or create e-invoices in the chat – without programming.
  • Developers who want to give their AI assistant tools for e-invoices. For your own applications, the REST API is available with an API key. API for developers

Setup step by step

  • Server URL: https://www.e-rechnungsfreund.de/api/v1/mcp/
  • Sign-in: with your account (OAuth 2.1) or with the HTTP header Authorization: Api-Key <key>
  1. Add the server to your assistant

    Claude (claude.ai, Claude Desktop)

    Add the server in Claude as a custom connector: under Customize → Connectors select Add → Add custom connector, enter the server URL and confirm. Claude then opens our sign-in page; sign in and allow access. You do not need an API key or any additional software.

    Connected AI assistants are listed in your account under API Keys, where you can revoke each access on its own. Connected AI assistants

    Claude Code and other clients

    Clients that support remote MCP servers with their own headers can also use an API key instead of signing in, for example Claude Code:

    claude mcp add --transport http e-invoice https://www.e-rechnungsfreund.de/api/v1/mcp/ --header "Authorization: Api-Key YOUR_API_KEY"

    The key is stored in the configuration of your assistant. Create a separate key for it, so that you can revoke it on its own. API Keys

  2. Ask your assistant
    For example: “Check the attached e-invoice” or “Create an e-invoice for …” with the invoice data. The assistant then calls the matching tool of the MCP server.

Permissions and limits

  • Pro and Business: create and check e-invoices and explain validation rules (all tools).
  • Free and Starter: check e-invoices and explain validation rules (validate_e_invoice, explain_validation_rule).

With sign-in and with an API key, the MCP server uses the same plan permissions and rate limits as the REST API: each message to the server counts as a request; checking and creating files also count towards the limit for resource-intensive requests and towards the monthly validations or invoices of your plan.

View plans with API access · Rate limits

Privacy

When you use the MCP server, you pass invoice data to your AI assistant; its provider processes them according to its own privacy terms, and you decide which data you share there. The validation and creation of the e-invoice runs on our server, as with the API; we do not pass invoice data on to AI services.

Privacy policy · Security and data protection

Frequently asked questions

What is an MCP server?

MCP (Model Context Protocol) is a protocol with which AI assistants call tools of other services. The MCP server of E-Rechnungsfreund provides three tools: checking e-invoices, explaining validation rules and creating ZUGFeRD or XRechnung files.

Which AI assistants can I use?

This page describes the setup for Claude (claude.ai, Claude Desktop) and Claude Code. Other clients with support for remote MCP servers and sign-in via OAuth or custom HTTP headers may also work.

Which plan do I need?

Checking with validate_e_invoice is also possible with API access for checking only (Free and Starter); creating with create_e_invoice requires a plan with full API access (Pro and Business). The scope of each plan is shown on the pricing page.

Do I need to program anything?

No. You enter the server URL in your assistant and sign in with your account, or you enter your API key in its configuration – no programming needed.

Does using the MCP server count towards my plan?

Yes. With sign-in and with an API key, the MCP server uses the same plan permissions and rate limits as the REST API; checking and creating count towards the monthly validations or invoices of your plan.

Is my invoice data passed on to AI services?

We do not pass invoice data on to AI services; checking and creating run on our server. What you enter in your AI assistant is processed by its provider according to its own privacy terms.

View plans with API access