Removing Mana from an agent disconnects that agent. It deletes nothing: the memories your organization keeps stay where they are, and an admin revokes a person's access from Settings.
Paste this into the agent you want to disconnect. It removes the server, clears the credentials, and takes out anything the agent added to your instruction files.
It works in an agent that runs on your own machine. In claude.ai and ChatGPT you remove the connector yourself, in Settings; skip to the section below.
Claude Code:
claude mcp logout mana claude mcp remove mana -s user
Codex:
codex mcp logout mana codex mcp remove mana
OpenCode:
opencode mcp remove mana
claude.ai and ChatGPT: open Settings, then Connectors, and remove the Mana connector. Both were added by hand, so both are removed by hand; the prompt above cannot do it for you.
If you let an agent add the rules to a global instruction file, the block sits between <!-- mana:begin --> and <!-- mana:end --> in one of these. Delete the block and its markers; leave the rest of the file alone.
~/.claude/CLAUDE.md for Claude Code~/.codex/AGENTS.md for Codex~/.config/opencode/AGENTS.md for OpenCodeDisconnecting a client does not end your access. An admin revokes a grant from Settings, which stops every token that grant issued.
Disconnect Mana from this agent and undo what it added, then tell me exactly what you changed. 1. Remove the Mana MCP server from this agent’s configuration, and clear the credentials it stored. 2. If my global agent instruction file holds a block between <!-- mana:begin --> and <!-- mana:end -->, delete that block and its markers and leave the rest of the file as it was: ~/.claude/CLAUDE.md for Claude Code, ~/.codex/AGENTS.md for Codex, ~/.config/opencode/AGENTS.md for OpenCode. 3. Delete nothing in the store. The memories my organization keeps stay where they are; an admin revokes a person’s access from Settings.