# bigapi MCP server

> Converts AI-generated content into finished files through operations like PDF manipulation, image processing, document conversion, and redaction.

- Repository: https://github.com/BiGapi-2026/bigapi-mcp
- Page: https://hostedmcp.org/servers/bigapi-2026/bigapi-mcp
- Transport: stdio
- Stars: 0
- License: MIT
- Latest version: 0.9.1

## Install

### Claude Code

```sh
claude mcp add --env 'BIGAPI_KEY=<YOUR_BIGAPI_KEY>' bigapi-mcp -- npx -y @bigapi/mcp
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "bigapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bigapi/mcp"
      ],
      "env": {
        "BIGAPI_KEY": "<YOUR_BIGAPI_KEY>"
      }
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "bigapi-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@bigapi/mcp"
      ],
      "env": {
        "BIGAPI_KEY": "<YOUR_BIGAPI_KEY>"
      }
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"bigapi-mcp","type":"stdio","command":"npx","args":["-y","@bigapi/mcp"],"env":{"BIGAPI_KEY":"<YOUR_BIGAPI_KEY>"}}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "bigapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bigapi/mcp"
      ],
      "env": {
        "BIGAPI_KEY": "<YOUR_BIGAPI_KEY>"
      }
    }
  }
}
```

### Codex

```sh
codex mcp add bigapi-mcp --env 'BIGAPI_KEY=<YOUR_BIGAPI_KEY>' -- npx -y @bigapi/mcp
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.bigapi-mcp]
command = "npx"
args = ["-y", "@bigapi/mcp"]

[mcp_servers.bigapi-mcp.env]
BIGAPI_KEY = "<YOUR_BIGAPI_KEY>"
```

### Gemini CLI

```sh
gemini mcp add -s user -e 'BIGAPI_KEY=<YOUR_BIGAPI_KEY>' bigapi-mcp npx -- -y @bigapi/mcp
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "bigapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bigapi/mcp"
      ],
      "env": {
        "BIGAPI_KEY": "<YOUR_BIGAPI_KEY>"
      }
    }
  }
}
```

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `BIGAPI_KEY` | no | yes | Optional API key (otherwise call the get_access tool) |

## Tools (5)

- `find_tool`: Find the right bigapi operation for a task. Describe what you need in plain words, English or German – "convert a png to webp", "remove customer names from a contract", "extract the ZUGFeRD invoice XML" – and get the matching operations with their parameters, a ready-to-run example, the price and a guide link. It recommends only: it never touches your files and never spends credit; run what it names with run_operation. Free and no API key needed, so it is also the cheapest way to see what bigapi covers. Start here whenever you are unsure which operation fits, and skip it when you already know the operation name. If nothing fits, the answer says so plainly instead of guessing.
- `run_operation`: Run any bigapi operation on real files: merge or redact a PDF, OCR a scan, convert an image, chunk text for embeddings, read a ZUGFeRD invoice, sign an image as AI-generated. Take the operation name from find_tool (e.g. "pdf/merge", "ocr", "text/chunk"). Uploads are local file paths. A file result is written to output_path, or to a temporary file when you omit it, and the path comes back with size and content type; a data result comes back as JSON. $0.01 per operation flat, no subscription, and failed calls cost nothing. This one executor covers every operation, including ones added after your client started – enable_tools only adds convenience wrappers around it. Files are processed in Germany, deleted right after delivery, and every operation ships with a published proof that it does what it promises.
- `enable_tools`: Add the dedicated tools for specific operations to this session, e.g. ["pdf_redact","einvoice_validate"], or ["all"] for every operation. Tools for every operation in the live bigapi catalogue are available, including ones added after this server was released. bigapi starts lean – only find_tool, run_operation, get_access and get_balance are listed – so your context stays free. You rarely need this: every operation already runs through run_operation. Reach for it when you will call the same operation many times and want its parameters spelled out in your tool list. Names come from find_tool; unknown names are reported back and skipped while the rest are still enabled. The effect lasts for this session, adds to what is already enabled, and cannot be undone from here – restart the server for the lean list again.
- `get_access`: Get a bigapi API key for this machine. Call this once when no key is configured; other bigapi tools fail with "no API key" until you do. Creates a NEW free key (no signup, no credit card) and stores it in the local config file, where every bigapi tool picks it up. Calling it again creates an additional key rather than returning the existing one – use get_balance to check the key you already have. The new key includes 100 free operations, then $0.01 per operation from a prepaid balance; neither expires. Needs network access to api.bigapi.dev.
- `get_balance`: Check the bigapi key that is currently configured: remaining credit, free operations left, monthly cap and spend so far this month. Read-only, free, and a snapshot of this moment – the numbers move as operations run. Use it to confirm a key works, before a large batch, or when an operation reports a low balance. It does not create keys (that is get_access) and does not list past operations.

## FAQ

### Do I need an API key to start?

No, you do not need an API key upfront; the agent can call the get_access tool to obtain one.

### Where are the files processed and stored?

Servers are located in Germany and follow GDPR; files are deleted after delivery.

### Can I use this without the MCP server?

Yes, you can use plain HTTP with tools like n8n, Make, Zapier, or LangChain.
