fetch_metadata — ToolSnap MCP MCP Tool Read-only
fetch_metadata
(fetch metadata) is one of 17 tools on the
ToolSnap MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fetch_metadata from your client
- Claude Code ToolSnap MCP fetch_metadata run in your project directory
- Claude Desktop ToolSnap MCP fetch_metadata ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ToolSnap MCP fetch_metadata ~/.cursor/mcp.json
- VS Code ToolSnap MCP fetch_metadata .vscode/mcp.json
- Zed ToolSnap MCP fetch_metadata ~/.config/zed/settings.json
- Windsurf ToolSnap MCP fetch_metadata ~/.codeium/windsurf/mcp_config.json
- Cline ToolSnap MCP fetch_metadata ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ToolSnap MCP fetch_metadata ~/.gemini/settings.json
- Grok ToolSnap MCP fetch_metadata .mcp.json (in your project root)
- ChatGPT ToolSnap MCP fetch_metadata Settings → Connectors → Advanced → Developer mode
- Claude.ai ToolSnap MCP fetch_metadata Settings → Connectors → Add custom connector
- LangChain ToolSnap MCP fetch_metadata pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http toolsnap-mcp https://mcp.toolsnap.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.