Converts AI-generated content into finished files through operations like PDF manipulation, image processing, document conversion, and redaction.
Also known as BiGapi-2026/bigapi-mcp, bigapi-mcp, @bigapi/mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- 585
- Latest version
- 0.9.1
- Last commit
- Nov 8, 2026
- License
- MIT
What is bigapi MCP?
bigapi converts AI-generated content into finished files through operations like PDF manipulation, image processing, document conversion, and redaction.
Summary generated from the project's README
About bigapi MCP server
Transforming AI-generated text and data into professional files is what this server enables for developers using Claude Desktop, Cursor, or Windsurf. It acts as an output layer that performs complex file manipulations that large language models cannot execute alone, such as PDF redaction, image processing, and document conversion. By connecting via HTTPS, your agent can merge PDFs, convert Office documents to PDF, or generate screenshots from URLs.
The server operates with a lean architecture to preserve your context window, starting with only five tools like find_tool and run_operation. You can load more specific tools on demand using enable_tools. It requires Node 18+ and can be set up without an upfront API key by having the agent call get_access. Operations are priced at $0.01 each, with the first 100 operations provided for free. All processing occurs on servers in Germany to support GDPR compliance, and files are deleted after delivery.
What you can do with it
- 1Redact sensitive PDF informationAsk the agent to remove private text from a document by using the redaction tool to ensure data is provably gone.
- 2Convert documents to MarkdownInstruct your AI client to transform complex PDF files or Office documents into clean Markdown for easier processing.
- 3Generate visual web contentRequest a full-page screenshot of a specific URL or render HTML into a high-quality PNG image.
- 4Apply AI transparency standardsEnsure your generated images comply with regulations by signing them with C2PA credentials and adding visible labels.
Written from the project's README. Every use case is checked against a quote from it.
How to install bigapi MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall bigapi MCP in Claude Code
$ claude mcp add --env 'BIGAPI_KEY=<YOUR_BIGAPI_KEY>' bigapi-mcp -- npx -y @bigapi/mcpInstall bigapi MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"bigapi-mcp": {
"command": "npx",
"args": [
"-y",
"@bigapi/mcp"
],
"env": {
"BIGAPI_KEY": "<YOUR_BIGAPI_KEY>"
}
}
}
}Install bigapi MCP in VS Code
.vscode/mcp.json
{
"servers": {
"bigapi-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@bigapi/mcp"
],
"env": {
"BIGAPI_KEY": "<YOUR_BIGAPI_KEY>"
}
}
}
}Install bigapi MCP in VS Code CLI
$ code --add-mcp '{"name":"bigapi-mcp","type":"stdio","command":"npx","args":["-y","@bigapi/mcp"],"env":{"BIGAPI_KEY":"<YOUR_BIGAPI_KEY>"}}'Install bigapi MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"bigapi-mcp": {
"command": "npx",
"args": [
"-y",
"@bigapi/mcp"
],
"env": {
"BIGAPI_KEY": "<YOUR_BIGAPI_KEY>"
}
}
}
}Install bigapi MCP in Codex
$ codex mcp add bigapi-mcp --env 'BIGAPI_KEY=<YOUR_BIGAPI_KEY>' -- npx -y @bigapi/mcpInstall bigapi MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.bigapi-mcp] command = "npx" args = ["-y", "@bigapi/mcp"] [mcp_servers.bigapi-mcp.env] BIGAPI_KEY = "<YOUR_BIGAPI_KEY>"
Install bigapi MCP in Gemini CLI
$ gemini mcp add -s user -e 'BIGAPI_KEY=<YOUR_BIGAPI_KEY>' bigapi-mcp npx -- -y @bigapi/mcpInstall bigapi MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"bigapi-mcp": {
"command": "npx",
"args": [
"-y",
"@bigapi/mcp"
],
"env": {
"BIGAPI_KEY": "<YOUR_BIGAPI_KEY>"
}
}
}
}Configuration
BIGAPI_KEYSecretOptional API key (otherwise call the get_access tool)
| Name | Description | |
|---|---|---|
| BIGAPI_KEY | Optional API key (otherwise call the get_access tool) | Secret |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@bigapi/mcp
MCP server for bigapi.dev – the output layer for AI agents.
Your agent produced something. bigapi turns it into a finished file – and reads files back in. Merge, redact, OCR, convert, sign, validate: the operations an LLM cannot do itself, over plain HTTPS, with one key, nothing to install server-side.
$0.01 per operation. 100 free. Free operations and balance never expire. Failed calls are free. Servers in Germany, GDPR, files deleted after delivery. Every operation ships with a published proof that it does what it promises.
Also listed in the official MCP Registry as dev.bigapi/mcp.
Lean by default
The server starts lean: it lists five tools, so your context stays free.
| Tool | What it does |
|---|---|
find_tool |
Describe your task in plain words, get the matching operation with a ready-to-run example. Free, no key. |
run_operation |
Run any bigapi operation by name, including ones added after your client started. |
enable_tools |
Load dedicated tools on demand, e.g. ["pdf_redact","einvoice_validate"] or ["all"]. Built from the live catalogue, so new operations appear without an update. |
get_access / get_balance |
Get a free key, check credit. |
All 60+ operations are available from the first second through run_operation; the dedicated
tools are a convenience, not a requirement. Want the full list right away?
Set BIGAPI_TOOLS=all in the server environment.
Why: every tool definition costs context in your client, and a model choosing between five descriptions picks better than one scanning forty-six.
What you can run
All 60+ operations, including e-invoices (XRechnung, ZUGFeRD), bank statements and PDF accessibility checks, go through run_operation (or their own tool after enable_tools).
Ask find_tool in plain words instead of memorising this list:
- PDF basics — merge, split, rotate, compress, page info, outline, compare, linearize
- PDF content — to Markdown, to images, extract tables, extract attachments (ZUGFeRD / Factur-X invoice XML)
- PDF safety — redact (rasterise and rebuild, text provably gone), sanitize (JavaScript, actions, embedded files), password on/off, verify signature
- PDF archival — PDF/A-2b with embedded fonts and an output intent, checked with veraPDF
- Documents — Office and e-books to PDF or Markdown (DOCX, XLSX, PPTX, ODT, EPUB), Markdown to Word, .eml to PDF
- Web and rendering — HTML/Markdown/URL to PDF or PNG, full-page screenshots with device presets, HTML or URL to clean Markdown, Handlebars templates, charts, QR codes
- Images — resize, crop, convert (WebP/AVIF/…), compress, strip metadata, watermark, image info
- AI transparency — C2PA Content Credentials sign and verify, visible "AI-generated" label with EXIF marking (EU AI Act Art. 50)
- Text for RAG — token-based chunking, heading-aware, with overlap
- Account — free key, balance, usage, monthly cap, pricing
Install
Requires Node 18+. No API key needed up front – the agent can call get_access itself.
Claude Desktop
claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"bigapi": {
"command": "npx",
"args": ["-y", "@bigapi/mcp"]
}
}
}
Restart Claude Desktop. Then: "Get bigapi access and render this text as a PDF on my Desktop."
Cursor / Windsurf / Cline
Same block in the respective MCP settings (.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, Cline → MCP Servers → Configure).
With an existing key
"bigapi": { "command": "npx", "args": ["-y", "@bigapi/mcp"], "env": { "BIGAPI_KEY": "bigapi_..." } }
How files work
Inputs are local paths (/Users/me/report.pdf, C:\Users\me\scan.pdf). Outputs are written to output_path if given, otherwise to a temp folder (BIGAPI_OUTPUT_DIR to change). Every result includes the cost, what it was charged from, and the remaining balance.
Pricing
Flat $0.01 per operation – every operation, no exceptions (per page for ocr, office_to_pdf, pdf_to_markdown, pdf_extract_tables, pdf_compare and pdf_redact). Prepaid from $5 – no subscription, no signup, balance never expires, failed calls are free. Machine-readable: get_pricing or GET /v1/pricing.
Environment
| Variable | Default | Purpose |
|---|---|---|
BIGAPI_KEY |
– | Use this key instead of the stored one |
BIGAPI_CONFIG_DIR |
~/.bigapi |
Where get_access stores the key (config.json, mode 600) |
BIGAPI_OUTPUT_DIR |
OS temp dir | Default output folder |
BIGAPI_URL |
https://api.bigapi.dev |
API base (for self-hosting / testing) |
Without MCP
Plain HTTP works everywhere (n8n, Make, Zapier, LangChain, your 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 · Docs: https://api.bigapi.dev/docs · Guides: https://bigapi.dev/guides/ · llms.txt: https://api.bigapi.dev/llms.txt
License
MIT
bigapi MCP questions
How do I add bigapi MCP to Claude Code?
Run claude mcp add --env 'BIGAPI_KEY=<YOUR_BIGAPI_KEY>' bigapi-mcp -- npx -y @bigapi/mcp in your terminal. Add --scope user to make it available in every project.
How do I add bigapi MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
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.