MCP.Market

Pluggy MCP server

by codespar·io.github.codespar/mcp-pluggy·v0.1.2·271 stars
No reviews yet

MCP server for Pluggy — Open Finance Brasil aggregator: accounts, transactions, payment initiation

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Established

271 stars40 downloads/wk

Reviews

Write one

Nobody has reviewed Pluggy yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pluggy tools (16, 5 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • create_connect_tokenwrite action

    Mint a connect token for embedding the Pluggy Connect widget on the client. Pluggy endpoint: POST /connect_token.

  • create_itemwrite action

    Create a new bank connection (item) for a connector. Pluggy endpoint: POST /items.

  • create_payment_intentwrite action

    Create a payment intent for Pluggy Payments (PISP). Pluggy endpoint: POST /payments/intents.

  • delete_itemwrite action

    Delete a bank connection (revokes credentials, removes accounts/transactions). Pluggy endpoint: DELETE /items/{id}.

  • get_account

    Get a single account by id. Pluggy endpoint: GET /accounts/{id}.

  • get_connector

    Get a single connector definition by id. Pluggy endpoint: GET /connectors/{id}.

  • get_item

    Fetch a single bank connection by id. Pluggy endpoint: GET /items/{id}.

  • get_payment_intent

    Fetch the current status of a payment intent. Pluggy endpoint: GET /payments/intents/{id}.

  • get_transaction

    Get a single transaction by id. Pluggy endpoint: GET /transactions/{id}.

  • list_accounts

    List accounts (checking, savings, credit card, investment) tied to an item. Pluggy endpoint: GET /accounts?itemId=...

  • list_categories

    List Pluggy's transaction categorization taxonomy. Pluggy endpoint: GET /categories.

  • list_connectors

    Lists supported Brazilian banks (connectors). Pluggy endpoint: GET /connectors. Optional filters: name, types (e.g. PERSONAL_BANK, BUSINESS_BANK), countries (BR), sandbox.

  • list_identities

    Fetch identity data (legal name, document, address) for an item. Pluggy endpoint: GET /identity?itemId=...

  • list_items

    List bank connections (items) owned by the application. Pluggy endpoint: GET /items.

  • list_transactions

    List transactions for an account in a date range. Pluggy endpoint: GET /transactions?accountId=&from=&to=.

  • update_itemwrite action

    Refresh / update credentials for an existing bank connection. Pluggy endpoint: PATCH /items/{id}.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 29 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Pluggy compares

Against every graded Finance MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 73% of 1,759 Finance servers
Tools
16
the typical Finance server has 8
Tools that change things
31%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
271
more than 95% of 945 Finance servers
Downloads a week
40
more than 33% of 422 Finance servers with a package

What its tools let an agent do: 11 read · 3 create · 1 change · 1 delete

Install Pluggy in Claude Code, Cursor or VS Code

Runs npx -y @codespar/mcp-pluggy on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-pluggy -- npx -y @codespar/mcp-pluggy
Add to Cursor

What the publisher says

From the Pluggy repository's README, as published. We do not edit it. Read it on GitHub

MCP Dev LATAM 🌎 Every commerce API your AI agent needs to run a business in Latin America. Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols. MCP servers for LATAM commerce · live in the official MCP Registry · MIT License Machine-readable catalog: codespar.dev/api/servers Catalog · Quick Start · Agentic Protocols · All Servers · Contribute

The Problem

AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).

Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with each other or with the regional rails businesses actually run on.

MCP Dev LATAM bridges both gaps. Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.

The Solution

Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.

🛒 Customer places order
  → 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop)
  → 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io)
  → 📦 Agent generates shipping label (Melhor Envio / Skydropx)
  → 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud)
  → 📊 Agent records in ERP (Omie / Bling / Tiny)
  → 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)

Six systems. Zero human intervention. One agent.

Agentic Payment Protocols

Four servers for the emerging agentic payment stack:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Pluggy: common questions

Is Pluggy MCP server safe?
Mostly: it is graded B (82/100). Read the Pluggy safety report
How do I install Pluggy?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Pluggy need an API key?
Yes. The registry entry asks for PLUGGY_CLIENT_ID, PLUGGY_CLIENT_SECRET.
Is Pluggy maintained?
The last commit was 69 days ago (2026-08-29). The latest release is v0.1.2.
What can I use instead of Pluggy?
Servers from other publishers that do the same job: MoneyMatter MCP server, Précis Finance MCP server and Finance Toolkit MCP server.
How does Pluggy compare with other Finance MCP servers?
safety score 82/100 (higher than 73% of 1,759 Finance servers); tools 16 (the typical Finance server has 8); tools that change things 31% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Pluggy

Same job from other publishers: the closest match first, then the best rated.

  • MoneyMatter
    Personal finance tracker: accounts, transactions, budgets, investments and analytics over OAuth.
    A
  • Précis Finance MCP
    Public read-only Précis Finance MCP demo with synthetic data; no account or credentials required.
    B
  • Finance Toolkit
    500+ transparent financial methods calculated from raw statements, not third-party endpoints.
    A
  • BankMCP™
    Read-only MCP server for your own bank accounts via Enable Banking. Self-hosted, one user.
    A
  • Yahoo Finance
    Access Yahoo Finance stock data, news, screeners, options, financials, and charts through MCP.
    A

More from codespar →