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