mcp_manifest — ToolSchema Forge MCP Tool
mcp_manifest
(mcp manifest) is one of 5 tools on the
ToolSchema Forge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call mcp_manifest from your client
- Claude Code ToolSchema Forge mcp_manifest run in your project directory
- Claude Desktop ToolSchema Forge mcp_manifest ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ToolSchema Forge mcp_manifest ~/.cursor/mcp.json
- VS Code ToolSchema Forge mcp_manifest .vscode/mcp.json
- Zed ToolSchema Forge mcp_manifest ~/.config/zed/settings.json
- Windsurf ToolSchema Forge mcp_manifest ~/.codeium/windsurf/mcp_config.json
- Cline ToolSchema Forge mcp_manifest ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ToolSchema Forge mcp_manifest ~/.gemini/settings.json
- Grok ToolSchema Forge mcp_manifest .mcp.json (in your project root)
- ChatGPT ToolSchema Forge mcp_manifest Settings → Connectors → Advanced → Developer mode
- Claude.ai ToolSchema Forge mcp_manifest Settings → Connectors → Add custom connector
- LangChain ToolSchema Forge mcp_manifest pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http toolschema-forge https://toolschema-forge.toolschemaforge.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.