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