MCP Server

The Pluggy Docs Model Context Protocol (MCP) server lets any AI agent read Pluggy's documentation, guides, API reference, changelog, recipes, and curated support Q&A directly at runtime. Instead of guessing from stale training data, your agent answers questions and writes integration code grounded in the live docs — with citations.

The server is hosted at:

https://v2.docs.pluggy.ai/api/mcp

It's a remote HTTP server: no installation, no API key, no login. Point any MCP-compatible client at that URL and it works.

Skills vs. MCP

The MCP server gives an agent live access to Pluggy's documentation at runtime. Agent Skills give the agent the know-how — the patterns and best practices — for building with Pluggy. They work independently, and even better together.

What you can do with it#

Once connected, ask your agent to build with Pluggy and it will pull the exact, current answer instead of hallucinating:

• "How do I create a connect token and open the Connect Widget?" → grounded steps from the live guides.
• "Show me the details of the createItem endpoint." → method, path, parameters, and schemas straight from the OpenAPI spec.
• "What changed in the last release for webhooks?" → the actual changelog entry, not a guess.
• "Why is my item stuck in WAITING_USER_INPUT?" → the curated, human-verified support Q&A that answered it before.
• "Write the code to list a user's transactions with pagination." → integration code that matches the current API.

Because it reads the same content published on this site, the answers stay correct as the docs evolve — you never re-teach your agent.

Available tools#

Connect it to your tool#

Pick your agent below. Everywhere you see it, the server URL is the same: https://v2.docs.pluggy.ai/api/mcp.

Claude Code#

claude mcp add --transport http pluggy-docs https://v2.docs.pluggy.ai/api/mcp

Add -s user to make it available in every project: claude mcp add -s user --transport http pluggy-docs https://v2.docs.pluggy.ai/api/mcp.

Claude Desktop#

Settings → Connectors → Add custom connector, name it Pluggy Docs, and paste https://v2.docs.pluggy.ai/api/mcp. Or edit claude_desktop_config.json:

{
  "mcpServers": {
    "pluggy-docs": {
      "type": "http",
      "url": "https://v2.docs.pluggy.ai/api/mcp"
    }
  }
}

ChatGPT (OpenAI)#

In Settings → Connectors → Advanced → Developer mode, add a connector with the URL https://v2.docs.pluggy.ai/api/mcp. (Custom remote MCP connectors are available on ChatGPT Plus/Pro/Business/Enterprise.) In a chat, enable the Pluggy Docs connector and ask away.

OpenAI Codex CLI#

Add to ~/.codex/config.toml:

[mcp_servers.pluggy-docs]
command = "npx"
args = ["-y", "mcp-remote", "https://v2.docs.pluggy.ai/api/mcp"]

Codex talks to local (stdio) MCP servers, so mcp-remote bridges to the hosted HTTP server.

Cursor#

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):

{
  "mcpServers": {
    "pluggy-docs": {
      "url": "https://v2.docs.pluggy.ai/api/mcp"
    }
  }
}

VS Code (GitHub Copilot agent mode)#

One command:

code --add-mcp '{"name":"pluggy-docs","type":"http","url":"https://v2.docs.pluggy.ai/api/mcp"}'

Or create .vscode/mcp.json in your workspace:

{
  "servers": {
    "pluggy-docs": {
      "type": "http",
      "url": "https://v2.docs.pluggy.ai/api/mcp"
    }
  }
}

Windsurf#

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "pluggy-docs": {
      "serverUrl": "https://v2.docs.pluggy.ai/api/mcp"
    }
  }
}

Gemini CLI#

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "pluggy-docs": {
      "httpUrl": "https://v2.docs.pluggy.ai/api/mcp"
    }
  }
}

Zed#

Add to your Zed settings.json:

{
  "context_servers": {
    "pluggy-docs": {
      "command": {
        "path": "npx",
        "args": ["-y", "mcp-remote", "https://v2.docs.pluggy.ai/api/mcp"]
      }
    }
  }
}

Any other MCP client#

If your client only supports local (stdio) servers, bridge to the hosted one with mcp-remote:

npx -y mcp-remote https://v2.docs.pluggy.ai/api/mcp

Clients that support remote Streamable HTTP servers can use the URL directly.

Test your setup#

Start a new chat with your agent and try:

Using the Pluggy docs MCP, how do I create a connect token and open the Connect Widget?

or

List the Pluggy API endpoints for Items and show me the details of createItem.

The agent should call the MCP tools and answer with citations from the live documentation. If nothing happens, restart the client after adding the server and confirm the URL is exactly https://v2.docs.pluggy.ai/api/mcp.

What it exposes#

The server covers everything published on this site:

• Documentation guides — concepts, quickstart, and integration guides (EN, PT, ES)
• API Reference — every endpoint from the OpenAPI spec, with parameters and schemas
• Changelog — release notes, breaking changes, and migration notes
• Recipes — step-by-step integration patterns and code examples
• Curated Q&A — real support questions answered and verified by the Pluggy team

It's read-only and public: the server exposes documentation, not your Pluggy account or data. To call the Pluggy API itself, use the API Reference with your own credentials.