MCP Tool Designer
The daily utility for AI Engineers. Generate valid tool schemas and configurations for Claude & Cursor instantly.
1. Define Your Tool
2. Server Settings (For Config)
node, npx, or python).-y @mcp/server or main.py).Where to paste this?
The Raw JSON Spec. Use this if you are building your own SDK or writing a custom tool handler from scratch.1. The JSON Spec (The Language)
This is the universal language of MCP. Whether your server is written in Node.js, Python, or Go, they all send this exact JSON structure to the AI. It acts as the "Passport" for your tool, allowing it to work across any MCP-compliant client like Claude, Cursor, or Windsurf.
2. Input Schema (The Guard)
The inputSchema is a standard JSON Schema. It doesn't just describe the tool; it enforces rules. If the AI tries to send a "number" when you asked for a "string", the protocol catches the error before your code even runs, preventing crashes.
3. The Config (The Bridge)
Claude Desktop needs a way to "find" and "launch" your server. The mcpServers config is the bridge. It tells the host application exactly which command to run in your terminal to start the conversation with your tool logic.
Where do these files live?
claude_desktop_config.json in your AppData/Library.C:/projects/my-mcp-server/index.js).