analyze_http_trace — OldWeb Logs MCP Tool
analyze_http_trace
(analyze http trace) 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 analyze_http_trace from your client
- Claude Code OldWeb Logs analyze_http_trace run in your project directory
- Claude Desktop OldWeb Logs analyze_http_trace ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OldWeb Logs analyze_http_trace ~/.cursor/mcp.json
- VS Code OldWeb Logs analyze_http_trace .vscode/mcp.json
- Zed OldWeb Logs analyze_http_trace ~/.config/zed/settings.json
- Windsurf OldWeb Logs analyze_http_trace ~/.codeium/windsurf/mcp_config.json
- Cline OldWeb Logs analyze_http_trace ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OldWeb Logs analyze_http_trace ~/.gemini/settings.json
- Grok OldWeb Logs analyze_http_trace .mcp.json (in your project root)
- ChatGPT OldWeb Logs analyze_http_trace Settings → Connectors → Advanced → Developer mode
- Claude.ai OldWeb Logs analyze_http_trace Settings → Connectors → Add custom connector
- LangChain OldWeb Logs analyze_http_trace 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.