| name | mcp-docs-and-implement |
| description | Implement using up-to-date docs or APIs via MCP. Use when the user wants to build something with current library/API docs (e.g. Context7, Stripe) and MCP is available. |
MCP Docs → Plan → Implement
This skill runs a workflow that uses MCP (Model Context Protocol) to fetch current documentation or API schemas, then plans and implements. Use when the project depends on external APIs or libraries and you want up-to-date references without pasting docs manually.
MCP best practice: check tool schema first
Before calling any MCP tool, read the tool’s descriptor/schema (e.g. under mcps/<server>/tools/<tool>.json) so you use correct parameters and required fields. Do not guess; check the schema.
Steps
-
Fetch docs or schema via MCP
- Use MCP tools or resources to get current docs or API schema for the library/API the user asked about (e.g. Context7 for library docs, Stripe MCP for payments).
- Use resources for read-only docs/data; use tools when you need to perform an action (query, API call). Check each tool’s schema before calling.
-
Plan (optional)
- Optionally invoke the planner subagent with the fetched context to refine scope and steps (e.g. “what endpoints exist?”). Planner inherits MCP; it can call the same servers if needed.
-
Implement
- Implement using the retrieved docs. Call MCP again during implementation if you need finer-grained details (signatures, options, examples).
- Follow project rules. Prefer checking tool schema before each MCP call.
-
Verify (optional)
- Optionally invoke the verifier subagent to confirm the implementation matches the docs or passes tool-based checks. Verifier can use MCP for compliance checks.
Notes
