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