bigapi
@bigapi/mcp
**bigapi.dev**용 MCP 서버 – AI 에이전트를 위한 출력 레이어.
Claude Desktop, Cursor, Cline, Windsurf 및 MCP를 지원하는 모든 에이전트에게 LLM이 스스로 할 수 없는 파일 작업을 제공합니다:
도구 | 기능 |
| HTML / Markdown / URL → PDF 또는 PNG (보고서, 인보이스, 제안서, 스크린샷) |
| PDF 기본 기능 |
| PDF 페이지 → JPEG/PNG, 예: 비전 모델로 문서를 확인하려는 경우 |
| 크기 조정, 자르기, 회전, 변환 (webp/avif/…), 압축, EXIF 제거, 워터마크 – 한 번의 호출로 |
| 형식, 크기, 색 공간, EXIF/ICC 존재 여부 |
| 무료 API 키, 즉시, 가입 없음 – 100회 무료 작업 |
| 계정 |
작업당 1센트. 100회 무료. 잔액은 만료되지 않습니다. 실패한 호출은 무료입니다. 서버는 독일에 있으며, 파일은 전송 후 삭제됩니다.
설치
Node 18+ 필요. 사전에 API 키가 필요 없음 – 에이전트가 get_access를 직접 호출할 수 있습니다.
Claude Desktop
claude_desktop_config.json (설정 → 개발자 → 구성 편집):
{
"mcpServers": {
"bigapi": {
"command": "npx",
"args": ["-y", "@bigapi/mcp"]
}
}
}Claude Desktop을 다시 시작하세요. 그런 다음: "bigapi 액세스 권한을 얻고 이 텍스트를 내 데스크톱에 PDF로 렌더링하세요."
Cursor / Windsurf / Cline
동일한 블록을 각 MCP 설정에 넣으세요 (.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, Cline → MCP 서버 → 구성).
기존 키가 있는 경우
"bigapi": { "command": "npx", "args": ["-y", "@bigapi/mcp"], "env": { "BIGAPI_KEY": "bigapi_..." } }Related MCP server: Filesystem MCP Server
파일 처리 방식
입력은 로컬 경로입니다 (/Users/me/report.pdf, C:\Users\me\scan.pdf). 출력은 output_path가 지정된 경우 해당 경로에, 그렇지 않으면 임시 폴더에 기록됩니다 (BIGAPI_OUTPUT_DIR로 변경 가능). 모든 결과에는 비용, 차감 출처, 남은 잔액이 포함됩니다.
환경 변수
변수 | 기본값 | 용도 |
| – | 저장된 키 대신 이 키를 사용 |
|
|
|
| OS 임시 폴더 | 기본 출력 폴더 |
|
| API 기본 URL (자체 호스팅 / 테스트용) |
MCP 없이 사용
일반 HTTP는 어디서나 작동합니다 (n8n, Make, Zapier, LangChain, 여러분의 코드):
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 · 문서: https://api.bigapi.dev/docs · llms.txt: https://api.bigapi.dev/llms.txt
라이선스
MIT
Available Tools
5 toolsenable_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
Scored across 5 tools
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.
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.
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.
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
Related MCP Connectors
MCP tools for AI agents: render URLs to image/PDF, check link health, convert HTML/CSV/JSON.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
Generate images, GIFs, videos, and PDFs from HTML, URLs, or templates — from your AI agent.
Htmlpdf Transform Mcp connects AI agents to real public APIs via MCP. Tools include
Related MCP Servers
AlicenseBqualityCmaintenanceThis repository is an example of how to create a MCP server for Qdrant, a vector search engine.21,572Apache 2.0- FlicenseAqualityBmaintenanceNode.js server implementing Model Context Protocol (MCP) for filesystem operations.70141,222,611 npm92,139-

Chroma MCP Serverofficial
AlicenseAqualityDmaintenanceA server that provides data retrieval capabilities powered by Chroma embedding database, enabling AI models to create collections over generated data and user inputs, and retrieve that data using vector search, full text search, and metadata filtering.1386,671 PyPI605Apache 2.0
@rendershot/mcp-serverofficial
AlicenseAqualityDmaintenanceEnables AI agents to capture screenshots and generate PDFs from URLs or HTML via the Rendershot API.43MIT