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