PicPay

Check your PicPay balance, cofrinhos, credit-card invoice, boletos, Pix limits and statement from your AI assistant.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the PicPay connector does

The PicPay MCP server connects a PicPay bank account to Claude, ChatGPT and any MCP-compatible agent. Its 13 tools read balances, cofrinhos, credit-card invoices, boletos, investments, Pix keys, contacts and limits, and up to 90 days of statement history. Every tool name ends in get or list, and PicPay states the integration performs no transactions.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

PicPay tools (13)

  • balance_account_get
  • bills_slips_list
  • cards_invoice_get
  • cards_invoice_summary_get
  • cards_invoice_transactions_list
  • cards_invoices_list
  • cards_list
  • investments_list
  • piggy_list
  • pix_contacts_list
  • pix_keys_list
  • pix_limits_get
  • statements_list

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Two advertised OAuth scopes exceed the published tool surface. piggy_bank.write and pix.write appear in the server's own descriptor while nothing in the 13 tools writes. PicPay publishes no explanation. Read the consent screen.
  • The vendor's material is Portuguese only. The tool reference, the connector page and the launch release are all Brazilian Portuguese. Every quotation on this page is our translation. For a non-Portuguese-reading team this is a real evaluation constraint.
  • Statement history is capped at 90 days, defaulting to 7 days and 15 records. Anything older is not reachable through this connector.
  • We could not read live tool schemas. The endpoint rejected an anonymous handshake and a syntactically valid junk bearer with different error bodies, so authentication is genuinely enforced. Parameter types and return fields on this page are PicPay's documentation, not observed responses, and documentation can drift from a running server.
  • No rate limits are published. PicPay's reference documents no request ceiling, quota or throttling behaviour for the connector. We do not know whether one exists.
  • No troubleshooting guidance is published. PicPay's documentation has no error-handling, failure-mode or reconnection section, so there is nothing to cite about what a failed call means.
  • Cofrinhos are capped at 10. piggy_list returns a flag for whether the 10-cofrinho limit has been reached, which is the connector telling you about a product limit rather than its own.
  • Availability was staged, not open. PicPay described a gradual rollout via an early-access list. Whether general availability has since been reached is not published.
  • Permission inheritance is undocumented. PicPay publishes no statement about whether the connector is bounded by the signed-in user's own permissions. Its absence is not evidence either way.
  • The connector supports one account. Nothing in the tool list accepts an account or profile selector, so it appears to address the single account you sign in as. PicPay does not state this.

Frequently asked questions

Can the PicPay MCP server move money out of your account?

No tool in the published inventory moves money. All 13 tool names end in get or list, and PicPay's per-tool reference documents only query parameters and return fields, with no amount or destination input anywhere. PicPay's own launch release states the integration is dedicated to queries and financial tracking, without transactions through the platform.

Why does PicPay advertise pix.write and piggy_bank.write scopes if nothing writes?

PicPay's OAuth descriptor lists seven scopes including two write scopes, which we read directly from the server on 2026-09-09. No published tool exercises them. PicPay has not explained the gap, so treat the scopes as capability the authorization layer is built for rather than behaviour the current connector performs, and re-read the consent screen before approving.

Do you need the PicPay app installed to connect the MCP server?

No. PicPay states the connection sends you to internet banking login and that having the app installed is not required. The connector uses the same security layers as the PicPay app, including facial biometric authentication. Access rolled out gradually through an early-access list at no cost, on both Android and iOS.

Is the PicPay MCP connector available outside Brazil?

PicPay is a Brazilian bank and the connector reaches a Brazilian account, so you need a PicPay account to use it. Every value it returns is in Brazilian reais and the features it exposes are Brazilian instruments: Pix, boletos, cofrinhos. PicPay does not publish any non-Brazilian availability for this connector.

How far back can the PicPay connector read your account statement?

Ninety days is the documented maximum. PicPay's reference for statements_list gives a default window of the last seven days, a ceiling of 90 days, and a default of 15 records per response. It also accepts a type filter that switches between recent entries and scheduled future ones.

What language is PicPay's MCP documentation written in?

Portuguese only. PicPay's tool reference, its connector landing page and its launch release are all in Brazilian Portuguese, and we found no English version of any of them. Field names in the returned data are mixed, with some in English and some in Portuguese such as saldo_total and total_investido, which matters when you write prompts against them.

Does the PicPay connector see more than you can see yourself?

There is no evidence it does, and the documented surface is narrower than the app. The 13 tools cover balance, cofrinhos, cards, invoices, investments, boletos, Pix keys, contacts and limits, and nothing else. PicPay has not published a written statement about permission inheritance, so we cannot confirm the boundary beyond what the tool list shows.

Which AI clients work with the PicPay MCP server?

Anthropic lists PicPay as working with Claude, the Claude API, Claude Code and Claude Desktop. PicPay separately shipped a ChatGPT plugin roughly two weeks before the Claude connector and says existing plugin users were enabled for Claude. The endpoint speaks standard streamable HTTP MCP, so other compliant clients should connect.

Sources

More Finance connectors

  • Affinity

    Search your CRM, prep for meetings and update deal records from your AI assistant.

  • Aiera

    Pull earnings-call transcripts, event calendars, SEC filings and company publications into your AI assistant.

  • Airwallex Developer

    Search Airwallex documentation and exercise a sandbox account from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put PicPay to work.

Connect PicPay once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.