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