changes.json — Crawler Log Triage MCP Resource

changes.json is one of 4 resources on the Crawler Log Triage MCP server. Connect the server and your client can attach it as context.

by client

How to attach changes.json from your client

• Claude Code Crawler Log Triage Resource/changes.json run in your project directory
• Claude Desktop Crawler Log Triage Resource/changes.json ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Crawler Log Triage Resource/changes.json ~/.cursor/mcp.json
• VS Code Crawler Log Triage Resource/changes.json .vscode/mcp.json
• Zed Crawler Log Triage Resource/changes.json ~/.config/zed/settings.json
• Windsurf Crawler Log Triage Resource/changes.json ~/.codeium/windsurf/mcp_config.json
• Cline Crawler Log Triage Resource/changes.json ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Crawler Log Triage Resource/changes.json ~/.gemini/settings.json
• Grok Crawler Log Triage Resource/changes.json .mcp.json (in your project root)
• ChatGPT Crawler Log Triage Resource/changes.json Settings → Connectors → Advanced → Developer mode
• Claude.ai Crawler Log Triage Resource/changes.json Settings → Connectors → Add custom connector
• LangChain Crawler Log Triage Resource/changes.json pip install langchain-mcp-adapters

Other resources on this server

• agents.json
• ip-ranges/all.json
• ua-regex.json

Crawler Log Triage also offers 1 prompt — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.