One MCP server.
Every session.

Full account control

One connection

The account server lists your visible sessions and routes tools with an explicit session_id, so parallel calls cannot drift into the wrong binary. Permissions are re-checked on every call.

Claude Code

Add the server

Sign in once, add the account endpoint, and use it across projects and sessions:

curl -X POST https://api.reverser.space/api/auth/login \
  -d '{"username":"you","password":"..."}'
# {"token":"...","user":{...}}

claude mcp add reverser --transport http \
  https://api.reverser.space/mcp/account \
  --header "Authorization: Bearer <token>"

Scope it with -s user for all your projects or -s project to share it through .mcp.json. The default is local to the current directory.

Cursor, Windsurf, and other clients

Or drop the URL in a config

Any MCP client that speaks HTTP takes the same account URL:

{
  "mcpServers": {
    "reverser": {
      "url": "https://api.reverser.space/mcp/account",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Confirm and clean up

Verify, use, remove

claude mcp list

Triage this binary, decompile the top-ranked function, and
explain what it does.

Rename FUN_00104020 to parse_header.

claude mcp remove reverser

Writes such as write_notes and renames need editor role on the target session. Account MCP lists the common surface once, then rejects any call above your current grant before it touches the session. For notes, read first and pass the returned revision when writing; if somebody saved meanwhile, the server returns a safe conflict so your agent can merge instead of overwriting their work.

When it does not connect

Troubleshooting