Menu
Plan an MCP server with clear tool scope, auth model, error behavior, evaluation approach, and rollout boundaries.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Handle /loop-style requests for finding, adapting, drafting, and preparing bounded agent loops without treating external loop catalogs as authorization.
Turn external skill, rule, plugin, MCP, task-memory, and multi-agent workspace patterns into safe fixture coverage rather than live dependencies.
Check whether host instruction surfaces such as AGENTS.md, CLAUDE.md, Codex agents, Cursor rules, Copilot instructions, and SKILL.md files have drifted apart.
Review skills generated from recorded workflows before they are installed, shared, or treated as reusable automation.
Review skills, agents, rules, plugins, and MCP/tool packs for license, source, script, permission, and supply-chain risk before adoption.
Choose the right task-memory and issue-state pattern for a repo: Beads, lightweight files, external tracker integration, or no durable task memory yet.
| name | mcp-server-planning |
| description | Plan an MCP server with clear tool scope, auth model, error behavior, evaluation approach, and rollout boundaries. |
Use this skill when a team wants to expose external capabilities through an MCP server.
Plan in this order:
Deliver:
Avoid:
