Add a single tool to one of this repo's existing MCP servers (google-docs, google-sheets, google-calendar, google-gmail, google-drive, clickup, slack, etc.). Wires the addTool block into src/<provider>/server.ts using the canonical pattern (Zod params, UserError handling, log.info breadcrumb, getXClient helper), classifies the tool as read or write in e2e/tools.ts, bumps the CLAUDE.md tool count, and optionally chains to /add-e2e-test to scaffold the smoke test. This skill is the single source of truth for the tool shape used across the codebase — use it whenever the user wants to add, create, or wire up a new MCP tool, action, endpoint, or operation, even when phrased indirectly ("expose X to Claude", "I want a tool that does Y"). Also use when invoked as `/add-mcp-tool <toolName> [provider]`.
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Scanned
boarlabsxyz/awesome-mcp
85cee7a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.