Adds a tool to an existing MCP server by defining its schema, handler, and registering it with input validation.
How this command is triggered — by the user, by Claude, or both
Slash command
/model-context-protocol:add-toolThe summary Claude sees in its command listing — used to decide when to auto-load this command
Add a new tool to an existing MCP server with proper schema and handler. ## Steps 1. Understand the tool requirements: 2. Define the tool schema: 3. Implement the tool handler: 4. Register the tool with the MCP server: 5. Add input validation: 6. Write a test for the tool handler. 7. Update the server documentation with the new tool. ## Format ## Rules - Tool names must be unique within the server. - Descriptions must be clear enough for an AI to use the tool correctly. - All required parameters must be validated before execution.
Add a new tool to an existing MCP server with proper schema and handler.
Tool: <name>
Description: <what it does>
Parameters:
- <name>: <type> (<required|optional>) - <description>
2plugins reuse this command
First indexed Mar 30, 2026
npx claudepluginhub costrict-plugins-repo/github-trending-plan --plugin model-context-protocol/add-toolAdds a tool to an existing MCP server by defining its schema, handler, and registering it with input validation.
/mcp-server-genGenerates a complete, production-ready MCP server for a given domain, including tools, resources, and prompts, plus a settings fragment and test suite.
/mcp-builderBuilds an MCP server using FastMCP. Accepts optional [server-name]; prompts for tools/resources to expose if omitted.
/add-toolGuides adding a new tool to DESIGN-OPS: identifies tool or pillar, evaluates MCP/API viability, provides connection instructions, updates config.