EOS Edge feed change log — endoflife.ai — Software Lifecycle Intelligence MCP Resource
EOS Edge feed change log
is one of 7 resources on the
endoflife.ai — Software Lifecycle Intelligence
MCP server. Connect the server and your client can attach it as context.
by client
How to attach EOS Edge feed change log from your client
- Claude Code endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log run in your project directory
- Claude Desktop endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log ~/.cursor/mcp.json
- VS Code endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log .vscode/mcp.json
- Zed endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log ~/.config/zed/settings.json
- Windsurf endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log ~/.codeium/windsurf/mcp_config.json
- Cline endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log ~/.gemini/settings.json
- Grok endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log .mcp.json (in your project root)
- ChatGPT endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log Settings → Connectors → Advanced → Developer mode
- Claude.ai endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log Settings → Connectors → Add custom connector
- LangChain endoflife.ai — Software Lifecycle Intelligence Resource/EOS Edge feed change log pip install langchain-mcp-adapters
Other resources on this server
endoflife.ai — Software Lifecycle Intelligence also offers 3 prompts — 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.