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