Background
EverMe integrates into a lot of agent tools by writing its own MCP-server entry (plus a per-tool agent id + token) into each tool's config. On a single machine I found EverMe wired into 8 places:
- Claude Code plugin (
~/.claude/: installed_plugins.json, known_marketplaces.json, settings.json, plugin cache + data dirs, everme.env)
- Codex
~/.codex/config.toml (marketplace + mcp_servers.everme + plugin entry)
- Cursor
~/.cursor/mcp.json
- Gemini CLI
~/.gemini/settings.json
- opencode
~/.config/opencode/opencode.json
- OpenClaw
~/.openclaw/openclaw.json (plugin allow-list + config block + contextEngine slot)
- Claude Desktop
claude_desktop_config.json
- hermes
~/.hermes/config.yaml
- npm globals:
@everme/cli, @everme/claude-code, @everme/memory-mcp, @everme/openclaw
Each integration carries a separate agent id + token.
Problem
There is no official uninstaller. everme.env itself notes that evercli plugin uninstall was retired in V1, so removing EverMe means manually hunting references across ~8 config files in three formats (TOML/JSON/YAML), deleting npm globals and plugin dirs, and then separately revoking each per-tool agent in the web UI. It's easy to leave live tokens behind.
Request
- An official uninstall command — e.g.
evercli uninstall --all — that reverses every integration EverMe created and revokes/deletes the corresponding agents server-side.
- Or/and a canonical "removal prompt" users can paste into any coding agent, listing every file and location EverMe touches so the agent can clean up reliably.
- Nice to have: have
install write a manifest of every file it modified, so uninstall is deterministic instead of best-effort grep.
Happy to help test.
Background
EverMe integrates into a lot of agent tools by writing its own MCP-server entry (plus a per-tool agent id + token) into each tool's config. On a single machine I found EverMe wired into 8 places:
~/.claude/:installed_plugins.json,known_marketplaces.json,settings.json, plugin cache + data dirs,everme.env)~/.codex/config.toml(marketplace +mcp_servers.everme+ plugin entry)~/.cursor/mcp.json~/.gemini/settings.json~/.config/opencode/opencode.json~/.openclaw/openclaw.json(plugin allow-list + config block +contextEngineslot)claude_desktop_config.json~/.hermes/config.yaml@everme/cli,@everme/claude-code,@everme/memory-mcp,@everme/openclawEach integration carries a separate agent id + token.
Problem
There is no official uninstaller.
everme.envitself notes thatevercli plugin uninstallwas retired in V1, so removing EverMe means manually hunting references across ~8 config files in three formats (TOML/JSON/YAML), deleting npm globals and plugin dirs, and then separately revoking each per-tool agent in the web UI. It's easy to leave live tokens behind.Request
evercli uninstall --all— that reverses every integration EverMe created and revokes/deletes the corresponding agents server-side.installwrite a manifest of every file it modified, so uninstall is deterministic instead of best-effort grep.Happy to help test.