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