Chatpack MCP vs CPFL: Download + OCR

A side-by-side look at the Chatpack MCP and CPFL: Download + OCR MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Chatpack MCP logoChatpack MCPDeveloper Tools · Local subprocess (stdio)Read-only MCP server for Chatpack documentation, framework setup guides, and React UI block source. Runs locally over stdio with npx -y @chatpack/mcp. Node.js 20 or later; MIT license; no account or API key required.87ExcellentAuth: no auth requiredCPFL: Download + OCR logoCPFL: Download + OCRDeveloper Tools · Remote HTTP/SSECPFL: Download + OCR, official-source lookup. Platform-hosted, pay per query with prepaid credit.55GoodAuth: not declared

Verdict: choose Chatpack MCP for developer tools work as a local process; choose CPFL: Download + OCR for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Chatpack MCP logoChoose Chatpack MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like search_docs, get_document, get_integration_guide.
Explore Chatpack MCP

CPFL: Download + OCR logoChoose CPFL: Download + OCR when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like contas_cpfl_download_ocr_consultar, show_version, report_bug.
Explore CPFL: Download + OCR

Feature & specification comparison

Rows where the two servers differ are marked.

SpecChatpack MCP logoChatpack MCPCPFL: Download + OCR logoCPFL: Download + OCR
CategoryDeveloper ToolsDeveloper Tools
Quality signal87/100 · Excellent55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars2240
Directory activity 4 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools57

Tools & capabilities

Chatpack MCP tools 5

  • search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.
  • get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.
  • get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.
  • list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.
  • get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.

CPFL: Download + OCR tools 7

  • contas_cpfl_download_ocr_consultarCPFL: Download + OCR, consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).
  • show_versionShow the current MCP platform and adapter versions.
  • report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
  • connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
  • toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
  • marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
  • authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Chatpack MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "chatpack-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chatpack/mcp"
      ]
    }
  }
}

CPFL: Download + OCR

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "cpfl-download-ocr": {
      "url": "https://api.mcp.ai/p_contas_cpfl_download_ocr"
    }
  }
}

Frequently asked questions

Chatpack MCP is categorized under Developer Tools and uses a local stdio subprocess. CPFL: Download + OCR belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Chatpack MCP for developer tools work and CPFL: Download + OCR for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Chatpack MCP is listed as free. Auth: no auth required. CPFL: Download + OCR has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add chatpack-mcp and cpfl-download-ocr as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Chatpack MCP has a quality signal of 87/100 (Excellent) with 4 views, 0 installs and 224 GitHub stars. CPFL: Download + OCR has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.