Skip to main content
Glama

@bigapi/mcp

MCP-Server für bigapi.dev – die Ausgabeschicht für KI-Agenten.

Gibt Claude Desktop, Cursor, Cline, Windsurf und jedem MCP-fähigen Agenten die Dateioperationen, die ein LLM nicht selbst ausführen kann:

Tool

Was es tut

render

HTML / Markdown / URL → PDF oder PNG (Berichte, Rechnungen, Angebote, Screenshots)

pdf_merge · pdf_split · pdf_rotate · pdf_compress

Die PDF-Grundlagen

pdf_to_images

PDF-Seiten → JPEG/PNG, z. B. um ein Dokument mit einem Vision-Modell zu betrachten

image_process

Größe ändern, zuschneiden, drehen, konvertieren (webp/avif/…), komprimieren, EXIF entfernen, Wasserzeichen – ein Aufruf

image_info

Format, Abmessungen, Farbraum, EXIF/ICC-Vorhandensein

get_access

Kostenloser API-Schlüssel, sofort, ohne Anmeldung – 100 kostenlose Operationen

get_balance · get_usage · set_monthly_cap · get_pricing

Konto

1 Cent pro Operation. 100 kostenlos. Guthaben verfällt nie. Fehlgeschlagene Aufrufe sind kostenlos. Server in Deutschland, Dateien werden nach der Zustellung gelöscht.

Installation

Erfordert Node 18+. Kein API-Schlüssel im Vorfeld nötig – der Agent kann get_access selbst aufrufen.

Claude Desktop

claude_desktop_config.json (Einstellungen → Entwickler → Konfiguration bearbeiten):

{
  "mcpServers": {
    "bigapi": {
      "command": "npx",
      "args": ["-y", "@bigapi/mcp"]
    }
  }
}

Starten Sie Claude Desktop neu. Dann: „Holen Sie sich bigapi-Zugriff und rendern Sie diesen Text als PDF auf meinem Desktop."

Cursor / Windsurf / Cline

Derselbe Block in den jeweiligen MCP-Einstellungen (.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, Cline → MCP-Server → Konfigurieren).

Mit einem vorhandenen Schlüssel

"bigapi": { "command": "npx", "args": ["-y", "@bigapi/mcp"], "env": { "BIGAPI_KEY": "bigapi_..." } }

Related MCP server: Filesystem MCP Server

So funktionieren Dateien

Eingaben sind lokale Pfade (/Users/me/report.pdf, C:\Users\me\scan.pdf). Ausgaben werden in output_path geschrieben, falls angegeben, andernfalls in einen temporären Ordner (BIGAPI_OUTPUT_DIR zum Ändern). Jedes Ergebnis enthält die Kosten, die Belastungsquelle und den verbleibenden Kontostand.

Umgebung

Variable

Standard

Zweck

BIGAPI_KEY

–

Diesen Schlüssel anstelle des gespeicherten verwenden

BIGAPI_CONFIG_DIR

~/.bigapi

Wo get_access den Schlüssel speichert (config.json, Modus 600)

BIGAPI_OUTPUT_DIR

OS-Temp-Verzeichnis

Standard-Ausgabeordner

BIGAPI_URL

https://api.bigapi.dev

API-Basis (für Self-Hosting / Tests)

Ohne MCP

Einfaches HTTP funktioniert überall (n8n, Make, Zapier, LangChain, Ihr Code):

curl -X POST https://api.bigapi.dev/v1/keys                       # → key
curl -o out.pdf https://api.bigapi.dev/v1/render \
  -H "Authorization: Bearer $KEY" -H "content-type: application/json" \
  -d '{"markdown":"# Hello from an agent"}'

OpenAPI: https://api.bigapi.dev/openapi.json · Doku: https://api.bigapi.dev/docs · llms.txt: https://api.bigapi.dev/llms.txt

Lizenz

MIT

Available Tools

5 tools
enable_toolsA

Add the dedicated tools for specific operations to this session, e.g. ["pdf_redact","ocr"], or ["all"] for every operation. 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.

Inputs: names (required).

find_toolA

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.

Inputs: query (required), limit.

get_accessA

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.

Inputs: name.

get_balanceA

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.

Inputs: no named parameters.

run_operationA

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.

Inputs: op (required), files, params, file_field, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct lifecycle role: discovery (find_tool), execution (run_operation), session convenience (enable_tools), key creation (get_access), and balance checking (get_balance). The descriptions explicitly cross-reference each other and state what they do not do, so there is little risk of an agent picking the wrong one.

    Naming Consistency5/5

    All five names follow a consistent snake_case verb_noun pattern (find_tool, run_operation, enable_tools, get_access, get_balance). The verbs are specific and match the action, and no style mixing or vague generic names appear.

    Tool Count5/5

    Five tools is well-scoped for a server that intentionally stays lean and dynamically exposes operations through find_tool/run_operation. Each tool covers a necessary concern: discovery, execution, optional tool enabling, access, and balance.

    Completeness5/5

    The core workflow is fully covered: obtain a key, find an operation, run it, and check credit/usage. The dynamic design means new operations don't require new server tools, so there are no obvious dead ends or missing lifecycle steps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers