Runs on your machine from its package; the steps are below.
At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @bigapi/mcp
MCP client config
{
"mcpServers": {
"bigapi-mcp": {
"command": "npx",
"args": [
"-y",
"@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.
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","ocr"] or ["all"]. |
get_access / get_balance | Get a free key, check credit. |
All 40+ 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.
All 40+ operations go through run_operation (or their own tool after enable_tools).
Ask find_tool in plain words instead of memorising this list:
Requires Node 18+. No API key needed up front – the agent can call get_access itself.
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."
Same block in the respective MCP settings (.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, Cline → MCP Servers → Configure).
"bigapi": { "command": "npx", "args": ["-y", "@bigapi/mcp"], "env": { "BIGAPI_KEY": "bigapi_..." } }
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.
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.
| 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) |
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
MIT