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