Skip to main content
Glama

@bigapi/mcp

MCP-сервер для bigapi.dev — выходной слой для ИИ-агентов.

Даёт Claude Desktop, Cursor, Cline, Windsurf и любому агенту с поддержкой MCP файловые операции, которые LLM не может выполнить самостоятельно:

Инструмент

Что делает

render

HTML / Markdown / URL → PDF или PNG (отчёты, счета, предложения, скриншоты)

pdf_merge · pdf_split · pdf_rotate · pdf_compress

Основы PDF

pdf_to_images

Страницы PDF → JPEG/PNG, например, чтобы просмотреть документ с помощью vision-модели

image_process

Изменение размера, обрезка, поворот, конвертация (webp/avif/…), сжатие, удаление EXIF, водяной знак — одним вызовом

image_info

Формат, размеры, цветовое пространство, наличие EXIF/ICC

get_access

Бесплатный API-ключ, мгновенно, без регистрации — 100 бесплатных операций

get_balance · get_usage · set_monthly_cap · get_pricing

Аккаунт

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). Каждый результат включает стоимость, источник списания и остаток баланса.

Окружение

Переменная

По умолчанию

Назначение

BIGAPI_KEY

–

Используйте этот ключ вместо сохранённого

BIGAPI_CONFIG_DIR

~/.bigapi

Где get_access хранит ключ (config.json, режим 600)

BIGAPI_OUTPUT_DIR

Временная папка ОС

Папка вывода по умолчанию

BIGAPI_URL

https://api.bigapi.dev

Базовый URL API (для самостоятельного хостинга / тестирования)

Без 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 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