Skip to content

Summary

Plaid's official sandbox MCP server: search Plaid docs, mint sandbox access tokens, generate mock financial data and fire test webhooks while building an integration.

Features

  • Search Plaid's product and API documentation from inside the agent
  • Provision working sandbox access tokens and item IDs on demand
  • Generate customised mock financial data for testing
  • Simulate sandbox webhook events against your own handler
  • Sandbox-only by design — no real account data is reachable
  • Ships alongside a Plaid CLI, a Dashboard MCP, an llms.txt index and drop-in rule files

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "Plaid Sandbox MCP Server" tools will be available.
{
  "mcpServers": {
    "plaid-sandbox-mcp": {
      "command": "uvx",
      "args": [
        "mcp-server-plaid"
      ],
      "env": {
        "PLAID_CLIENT_ID": "your_client_id",
        "PLAID_SECRET": "your_sandbox_secret"
      }
    }
  }
}

Description

Plaid's MCP server is aimed squarely at the build phase of a fintech integration rather than at production banking data. It ships inside the company's AI Coding Toolkit and gives a coding agent the three things that usually slow a Plaid integration down: accurate documentation, working sandbox credentials, and realistic test data.

The four tools
  • `search_documentation` — query Plaid's docs for a product or API endpoint. This matters more than it sounds: Plaid's API surface is wide and changes, and a model working from memory tends to invent endpoint shapes.
  • `get_sandbox_access_token` — provision a usable sandbox access token and item ID on demand, so the agent can write code that actually runs instead of leaving a placeholder.
  • `get_mock_data_prompt` — generate customised mock financial data (transactions, accounts, balances) for testing.
  • `simulate_webhook` — fire sandbox webhook events at your application so you can exercise the handler path without waiting for a real one.
Scope, and what it is not

This is the sandbox server. It does not read anyone's real bank accounts; it works against Plaid's sandbox environment with sandbox credentials from the developer dashboard. The wider AI Coding Toolkit around it also includes a Plaid CLI, a separate Dashboard MCP for runtime dashboard data, an llms.txt documentation index, and a rules/ directory of product-specific guides meant to be dropped into a CLAUDE.md or equivalent as project instructions.

Setup

Needs a sandbox client ID and secret from the Plaid dashboard, and uvx (or plain Python via python -m mcp_server_plaid). Credentials can be passed as CLI arguments or as PLAID_CLIENT_ID and PLAID_SECRET environment variables — prefer the environment variables, since argument lists show up in process listings. MIT licensed, and Plaid is explicit that correctness, security and compliance of anything you ship remain yours.

Modern Treasury's official MCP server, built on Code Mode: the agent writes TypeScript against the payments SDK and runs it in a sandbox instead of calling one tool per endpoint.

MCP: FetchSandbox MCP

by FetchSandbox

A sandbox for third-party API integrations: agents replay Stripe, GitHub, Twilio and 50+ other workflows — webhooks, retries and failure cases included — without touching the real API.

MCP: Brandfetch MCP

by Brandfetch

Official remote MCP server from Brandfetch that gives an agent real company logos, brand colours, fonts and merchant identification instead of guessed or hallucinated assets.

Featured

Drive live Jupyter notebooks from an agent — read and edit cells, execute code, see rich outputs, and run against local JupyterLab or a cloud sandbox.

Browse all MCP servers →