Invapi MCP Server

Extract, create, convert & validate invoices (UBL, CII, XRechnung, ZUGFeRD, PDF, Excel)

Local serverstdio

What is the Invapi MCP server?

Invapi MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Extract, create, convert & validate invoices (UBL, CII, XRechnung, ZUGFeRD, PDF, Excel).

What you get

MCP server for the Invapi E-Invoicing API — convert, validate, and extract invoices in UBL, CII, ZUGFeRD, Excel, and more.

What the assistant can call

Once Invapi is connected, these are the calls the assistant has available:

  • Conversion — The Conversion tool exposed by this server
  • Validation — The Validation tool exposed by this server
  • Extraction — The Extraction tool exposed by this server
  • User — The User tool exposed by this server
  • Batch — The Batch tool exposed by this server

Setting it up

The server ships on npm as @invapi/mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need one environment variable: INVAPI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Invapi's toolset — Conversion, Validation, Extraction and 2 more — is a fair guide to whether it matches your workflow. It is maintained by invapi-org; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the invapi mcp server does with a few real requests.

Available tools

ToolWhat it does
ConversionThe Conversion tool exposed by this server.
ValidationThe Validation tool exposed by this server.
ExtractionThe Extraction tool exposed by this server.
UserThe User tool exposed by this server.
BatchThe Batch tool exposed by this server.

How to install the Invapi MCP server

{
  "mcpServers": {
    "invapi": {
      "command": "npx",
      "args": ["-y", "@invapi/mcp-server"],
      "env": {
        "INVAPI_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
INVAPI_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Invapi to Conversion.
  • Use Invapi to Validation.
  • Use Invapi to Extraction.

Frequently asked questions

It connects Invapi to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (Conversion, Validation, Extraction, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Invapi directly.