get_site_metadata — NobodyNamed MCP Tool Read-only
get_site_metadata
(get site metadata) is one of 12 tools on the
NobodyNamed
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_site_metadata from your client
- Claude Code NobodyNamed get_site_metadata run in your project directory
- Claude Desktop NobodyNamed get_site_metadata ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NobodyNamed get_site_metadata ~/.cursor/mcp.json
- VS Code NobodyNamed get_site_metadata .vscode/mcp.json
- Zed NobodyNamed get_site_metadata ~/.config/zed/settings.json
- Windsurf NobodyNamed get_site_metadata ~/.codeium/windsurf/mcp_config.json
- Cline NobodyNamed get_site_metadata ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NobodyNamed get_site_metadata ~/.gemini/settings.json
- Grok NobodyNamed get_site_metadata .mcp.json (in your project root)
- ChatGPT NobodyNamed get_site_metadata Settings → Connectors → Advanced → Developer mode
- Claude.ai NobodyNamed get_site_metadata Settings → Connectors → Add custom connector
- LangChain NobodyNamed get_site_metadata pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nobodynamed https://nobodynamed.com/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.