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