changes.json — Agent Discovery Doctor - llms.txt, agent card, mcp.json MCP Resource
changes.json
is one of 4 resources on the
Agent Discovery Doctor - llms.txt, agent card, mcp.json
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 Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json run in your project directory
- Claude Desktop Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json ~/.cursor/mcp.json
- VS Code Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json .vscode/mcp.json
- Zed Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json ~/.config/zed/settings.json
- Windsurf Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json ~/.codeium/windsurf/mcp_config.json
- Cline Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json ~/.gemini/settings.json
- Grok Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json .mcp.json (in your project root)
- ChatGPT Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json Settings → Connectors → Add custom connector
- LangChain Agent Discovery Doctor - llms.txt, agent card, mcp.json Resource/changes.json pip install langchain-mcp-adapters
Other resources on this server
Agent Discovery Doctor - llms.txt, agent card, mcp.json 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.