Skip to main content
On /settings/my-account, at the bottom.
This removes the account, every MCP in it, and every teammate’s access, in one statement. There is no soft delete and nothing to restore from.

​
What it removes

Every foreign key cascades from the account, so one delete takes:
  • every MCP in the account
  • under each MCP: its ingest keys, its calls, its hourly counters, its sessions, its tool pairs, its alert rules and its registered tool list
  • every member row, including invitations that were never accepted
  • notification preferences for everyone in the account
  • the company profile
Everyone else in the account loses access at the same moment.

​
What it leaves

Sign-in identities. Identity belongs to Supabase Auth, and a person may hold membership of another account. What they lose here is this account, not their ability to sign in. Nothing recoverable. There is no export step built into the flow, so take what you need first.

​
Servers keep serving

A live server still wrapped with a key from a deleted account carries on handling tool calls exactly as before. Its flushes are rejected and dropped silently, because the SDK never throws and never retries. Remove MCPULSE_KEY from those environments when convenient. Nothing breaks if you don’t.

​
It is owner-only

Every other destructive action in MCPulse stops at admin, because those remove one thing and can be done again. This removes the account itself. It sits one rank above the rest.

​
It asks you to type the account name

Every other destructive confirm in MCPulse is a single click, which is right when the thing can be made again — and wrong here. This one asks you to type the account name first.

​
Deleting one MCP instead

If you want to stop tracking one server, delete the MCP. Siblings are untouched.