Integration

Pluggy Status integration

Pluggy Status is the public health feed of Pluggy, the Brazilian open-finance aggregator: read the overall platform status, the incidents affecting each bank connector right now (keyed by Pluggy connector id), or the full snapshot of every connector's health, 90-day history, infrastructure components and incident timelines. Use it to warn a user before they connect a degraded bank, or to explain a failed sync. The data describes banks and Pluggy's own services, never end users. No credential is needed: the three routes are public and cached for about 30 seconds by Pluggy. Pluggy's main API (accounts, transactions, payments) is a separate product that this integration does not cover.

Connect Pluggy Status How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Pluggy Status.Built from the 3 Pluggy Status tools below, on the connection you add once.

What you can do with Pluggy Status

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Connector incident, 1 operation

list_connector_incidentsList connector incidentsGETAgents: ask firstLists the incidents affecting each Pluggy bank connector right now, as a map keyed by connector id (each list worst-first). Only connectors with an active incident appear. A few KB, unlike get_status_snapshot.

Status snapshot, 1 operation

get_status_snapshotGet status snapshotGETAgents: ask firstReturns Pluggy's full status snapshot: each bank connector's health, 90-day history and uptime, 90 days of incidents, infrastructure components. About 700 KB: a chat call keeps only a few items per list, so prefer list_connector_incidents.

Status summary, 1 operation

get_status_summaryGet status summaryGETAgents: ask firstReturns Pluggy's overall status in one small object: status code (op, mn, dg, pt or mj), a ready label in pt, es and en, the count of open incidents (maintenance windows excluded) and when it was computed.

Use Pluggy Status from Claude Code, Cursor or Codex

Connect Pluggy Status in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Pluggy Status operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Pluggy Status

Create your workspace
Sign up free. Nothing to install.
Connect Pluggy Status once
Pluggy Status needs no credential, so its tools work immediately.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.