Agent skill · Coding
MCP setup planner
Picks MCP servers for a task, preferring ones published by the service's own vendor or listed in the official MCP registry, and writes the setup for Claude Code, Cursor or Codex with least-privilege scopes and environment variable placeholders, never inline secrets. Lists what each server can read and change. Use when asked which MCP servers to use, or to set up MCP for an agent.
The mcp-setup-planner/ folder with SKILL.md.
The skill itself. Agents read the name and description first and load the rest only when a task matches.
mcp-setup-planner/SKILL.md
---
name: mcp-setup-planner
description: Picks MCP servers for a task, preferring ones published by the service's own vendor or listed in the official MCP registry, and writes the setup for Claude Code, Cursor or Codex with least-privilege scopes and environment variable placeholders, never inline secrets. Lists what each server can read and change. Use when asked which MCP servers to use, or to set up MCP for an agent.
---
# MCP setup planner
Choose the fewest MCP servers that do the job, and set them up so they can do no more than the job needs.
## Steps
1. Restate the task and list the systems the agent must read from or act on (for example: GitHub issues, a Postgres database, Linear, the file system).
2. For each system, look for a server in this order: one published by the vendor itself, then one in the official MCP registry from a known publisher, then a widely used community server. Note the publisher, how it's run (local command or remote URL) and when it was last updated.
3. Decide the scopes: read-only unless the task needs writes; one repo, project or database schema rather than all of them; a dedicated token per server.
4. Write the config for the user's agent:
- Claude Code: `claude mcp add` commands or a project `.mcp.json`.
- Cursor: `.cursor/mcp.json`.
- Codex: the `[mcp_servers]` section of `~/.codex/config.toml`.
Put every secret in an environment variable placeholder such as `${GITHUB_TOKEN}`.
5. Write a table: server, publisher, what it can read, what it can change, the token's scopes, and how to revoke it.
6. List what to check after setup: the server shows as connected, a read-only call works, and a write is refused if it should be.
## Rules
- Never put a token, password or key in a config file or command. Placeholders only.
- Say when no trustworthy server exists, and suggest doing that part by hand instead of recommending an unknown one.
- Don't add servers the task doesn't need, even if they'd be "nice to have".
- Point out servers that can run shell commands or reach the network, and ask before including them.