Mcp Pluggy

io.github.codesparPublished by GitHub account codesparv0.1.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant query Brazilian Open Finance data through Pluggy: bank connections, accounts, transactions, identity, and payment intents.

What you can do
Wraps the Pluggy Open Finance Brasil aggregator API in 16 tools. It lists connectors and transaction categories, creates and manages bank connections (items), and reads accounts, transactions, and identity data. It also creates Pluggy Connect tokens and initiates or polls payment intents.
When to use it
Use it when an assistant needs Brazilian bank account, transaction, or identity data, or when building flows that initiate payments through Pluggy. Sandbox connectors with synthetic data are available for testing before production credentials are used.
Requirements
Runs locally over stdio, typically via npx @codespar/mcp-pluggy, so Node.js is needed. Requires a Pluggy account and the PLUGGY_CLIENT_ID and PLUGGY_CLIENT_SECRET environment variables; PLUGGY_API_BASE can override the default API base. Network access to the Pluggy API is required.
Before you install
PLUGGY_CLIENT_ID and PLUGGY_CLIENT_SECRET are secrets that grant access to financial data and must be kept out of shared configs. Tools can create, update, and delete bank connections, and create payment intents that may move money. Identity data includes legal name, document, and address, and account and transaction data is sent to Pluggy.

Installation

In SourceWeft

  1. Open Mcp Pluggy in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@codespar/mcp-pluggy

MCP server for Pluggy — Open Finance Brasil aggregator (ITP/TPP). Pluggy holds the ICP-Brasil certificate and runs Dynamic Client Registration with each Brazilian bank, so you integrate against one API instead of N.

Quick Start

Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "pluggy": {      "command": "npx",      "args": ["@codespar/mcp-pluggy"],      "env": {        "PLUGGY_CLIENT_ID": "your-client-id",        "PLUGGY_CLIENT_SECRET": "your-client-secret"      }    }  }}

Cursor / VS Code

Same config in .cursor/mcp.json or VS Code's MCP integration.

Tools (16)

Connectors + categories

ToolPluggy endpointNotes
list_connectorsGET /connectorsFilter by name / types / countries / sandbox
get_connectorGET /connectors/{id}Single connector definition
list_categoriesGET /categoriesTransaction categorization taxonomy

Connect token

ToolPluggy endpointNotes
create_connect_tokenPOST /connect_tokenEmbed Pluggy Connect widget on the client

Items (bank connections)

ToolPluggy endpointNotes
create_itemPOST /itemsNew bank connection from credentials
list_itemsGET /itemsLists existing connections
get_itemGET /items/{id}Single connection
update_itemPATCH /items/{id}Refresh credentials / trigger sync
delete_itemDELETE /items/{id}Revoke connection

Accounts + transactions + identity

ToolPluggy endpointNotes
list_accountsGET /accounts?itemId=...Checking / savings / credit / investment
get_accountGET /accounts/{id}Single account
list_transactionsGET /transactions?accountId=...Date-range filter
get_transactionGET /transactions/{id}Single transaction
list_identitiesGET /identity?itemId=...Legal name + document + address

Payments (PISP)

ToolPluggy endpointNotes
create_payment_intentPOST /payments/intentsInitiate a Pluggy Payments intent
get_payment_intentGET /payments/intents/{id}Poll status

Authentication

Pluggy uses an OAuth2 client-credentials flow:

  1. Client obtains an API key by POST /auth with clientId + clientSecret
  2. Subsequent requests include the API key as X-API-KEY

Issue credentials at the Pluggy dashboard:

Sandbox / Testing

Pluggy provides sandbox connectors with synthetic accounts and transactions. The sandbox uses the same API endpoint (https://api.pluggy.ai); the connector list returned by /connectors includes sandbox banks (Pluggy Bank, BR · Pluggy Bank).

Environment Variables

VariableRequiredDescription
PLUGGY_CLIENT_IDyesClient ID from the Pluggy dashboard
PLUGGY_CLIENT_SECRETyesClient secret from the Pluggy dashboard
PLUGGY_API_BASEnoOverride API base (default https://api.pluggy.ai)

Why use Pluggy via CodeSpar

If you only need the MCP server, install the package directly. If you're building a commerce agent that needs Pluggy + Pix + NF-e + WhatsApp + dashboard governance, look at the managed tier.

Enterprise

Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Source: packages/banking/pluggy/README.md at commit d0a519a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts