GoPluto AI MCP MCP Server

MCP for quick human experts. The gopluto ai mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.

What it actually does

Add use gopluto in your prompt (or set a rule once) and the assistant fetches live GoPluto context:

Its toolset

Everything the assistant can do here goes through one of these:

• resolve-gopluto-id — Resolve a package/service name to a GoPluto ID
• get-gopluto-docs — Fetch docs/snippets for a GoPluto ID
• search-providers — Query providers by skills/geo/budget
• create-service-request — Minimal payload helper
• Requirements — The Requirements tool exposed by this server
• Cursor — The Cursor tool exposed by this server
• Windsurf — The Windsurf tool exposed by this server
• Cline — The Cline tool exposed by this server
• Opencode — The Opencode tool exposed by this server
• Kiro — The Kiro tool exposed by this server
• Trae — The Trae tool exposed by this server

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration

You will need 6 environment variables: GOPLUTO_MCP_URL, GOPLUTO_AUTH_HEADER, GOPLUTO_API_KEY, GOPLUTO_TRANSPORT, YOUR_API_KEY, YOUR_REAL_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Any MCP‑capable client (Cursor, Claude Code, VS Code, Windsurf, Zed, etc.) - GoPluto API Key (keep client‑side) - Network access to https://api.gopluto.ai/mcp Auth header: gopluto-api-key: YOUR_API_KEY > If your client can’t attach headers to remote servers, use the included local stdio proxy (main.py) to add the header for you. ---

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. GoPluto AI MCP's toolset — resolve-gopluto-id, get-gopluto-docs, search-providers and 8 more — is a fair guide to whether it matches your workflow.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch GoPluto AI MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the gopluto ai mcp mcp server does with a few real requests.