Agents
MCP server
Connect Claude, Cursor, VS Code, ChatGPT, Codex, Gemini and other agents to dissolve.email with the hosted MCP server: install, sign in, scopes, limits and security.
The hosted Model Context Protocol server lets an AI agent make a throwaway address, use it in a sign-up form and read the code the site sends, by itself. There is nothing to run locally: it lives at mcp.dissolve.email, speaks Streamable HTTP statelessly, holds no data and calls the API with your own credential.
| Endpoint | Signs in with | Use it when |
|---|---|---|
https://mcp.dissolve.email/mcp-oauth | OAuth 2.1: the client opens a browser and you approve on app.dissolve.email | Almost always. Works on every plan. |
https://mcp.dissolve.email/mcp | An API key (sk_live_...) in X-API-Key or Authorization: Bearer | Headless agents, CI, clients without OAuth. Needs Pro or Business. |
The install guide, the Claude Code plugin and a skill that knows the sign-up workflow live in the public dissolve-mcp repository.
Install
Claude Code
The plugin from the dissolve-mcp repository adds the server and the sign-up skill:
/plugin marketplace add dissolve-email/dissolve-mcp
/plugin install dissolve@dissolveOr add the server alone, then run /mcp, pick dissolve and sign in:
claude mcp add --transport http dissolve https://mcp.dissolve.email/mcp-oauthclaude mcp add --transport http dissolve https://mcp.dissolve.email/mcp --header "X-API-Key: $DISSOLVE_API_KEY"Claude (claude.ai and Claude Desktop)
Settings, Connectors, Add custom connector. Name it dissolve.email, paste https://mcp.dissolve.email/mcp-oauth, press Add, then Connect. Claude opens the dissolve.email approval page in your browser.
Cursor
In ~/.cursor/mcp.json, or .cursor/mcp.json in a project. Cursor then shows Needs login under Settings, MCP; press it to sign in.
{
"mcpServers": {
"dissolve": { "url": "https://mcp.dissolve.email/mcp-oauth" }
}
}VS Code (GitHub Copilot agent mode)
In .vscode/mcp.json:
{
"servers": {
"dissolve": { "type": "http", "url": "https://mcp.dissolve.email/mcp-oauth" }
}
}Windsurf
In ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"dissolve": { "serverUrl": "https://mcp.dissolve.email/mcp-oauth" }
}
}ChatGPT
With developer mode on: Settings, Connectors, Create. Use https://mcp.dissolve.email/mcp-oauth and OAuth authentication.
OpenAI Codex CLI
In ~/.codex/config.toml, then run codex mcp login dissolve:
[mcp_servers.dissolve]
url = "https://mcp.dissolve.email/mcp-oauth"Gemini CLI
In ~/.gemini/settings.json:
{
"mcpServers": {
"dissolve": { "httpUrl": "https://mcp.dissolve.email/mcp-oauth" }
}
}Any other client
A client that speaks Streamable HTTP with OAuth finds everything by itself: its first call answers 401 with WWW-Authenticate: Bearer resource_metadata="https://mcp.dissolve.email/.well-known/oauth-protected-resource/mcp-oauth", which leads it to the authorization server at https://api.dissolve.email. Authentication describes the flow.
A client that only runs local (stdio) servers can use a bridge such as mcp-remote:
{
"mcpServers": {
"dissolve": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.dissolve.email/mcp-oauth"] }
}
}{
"mcpServers": {
"dissolve": {
"url": "https://mcp.dissolve.email/mcp",
"headers": { "X-API-Key": "sk_live_..." }
}
}
}What an agent does with it
create_identity(Pro and up) makes an inbox with a strong password and, if asked, a fictional persona. On Free,create_inboxmakes the address and the agent picks its own password.- The agent fills in the site's sign-up form with that address.
get_identity_code, orget_verification_codefor a plain inbox, waits for the code or magic link and returns it.save_to_vaultkeeps the email and password after the identity expires.
Inboxes and identities expire on their own; the plan sets how long. The playbooks show whole workflows.
Tools
26 tools, task-level first. Each needs the scope shown; the server lists only the tools a connection's scopes allow. MCP tools has every input, an example and the API request each one makes.
| Tool | What it does | Scope |
|---|---|---|
create_identity | Create a sign-up identity | identities:write |
get_identity_code | Get the verification code sent to an identity | messages:read |
get_verification_code | Get a verification code from an inbox | messages:read |
wait_for_message | Wait for an email | messages:read |
get_account | Get the account and its limits | profile |
list_domains | List email domains | any |
list_inboxes | List inboxes | inboxes:read |
get_inbox | Get an inbox | inboxes:read |
create_inbox | Create an inbox | inboxes:write |
extend_inbox | Extend an inbox | inboxes:write |
delete_inbox | Delete an inbox | inboxes:write |
create_alias | Add an alias to an inbox | inboxes:write |
delete_alias | Remove an alias | inboxes:write |
list_messages | List messages in an inbox | messages:read |
read_message | Read a message | messages:read |
list_attachments | List a message's attachments | messages:read |
list_labels | List labels | messages:read |
label_message | Label a message | messages:write |
unlabel_message | Remove a label from a message | messages:write |
list_identities | List identities | identities:read |
get_identity | Get an identity | identities:read |
update_identity | Extend or relabel an identity | identities:write |
delete_identity | Delete an identity | identities:write |
list_vault_entries | List saved credentials | vault:read |
get_vault_entry | Get a saved credential | vault:read |
save_to_vault | Save a credential | vault:write |
Scopes
An OAuth client that asks for no scope gets the MCP defaults: profile, inboxes:read, inboxes:write, messages:read, messages:write, identities:read and identities:write. Vault, webhook, rule and email scopes must be asked for, and vault access from an app dissolve.email has not verified needs a second confirmation on the consent page. An API key on /mcp has every scope. The full list is on Authentication.
Disconnect an app at any time under Connected apps: its tokens stop working at once.
Plans and limits
| Free | Pro | Business | |
|---|---|---|---|
OAuth (/mcp-oauth) | 30 calls a minute | 100 a minute | 1,000 a minute |
API key (/mcp) | No | 100 a minute | 1,000 a minute |
Identities (create_identity) | No | 10 at once | 50 at once |
| Longest wait in one call | None (checks once) | 30 s | 120 s |
The MCP server has no rate limit of its own: the API limits each credential, and a refusal says which limit was hit. Rate limits and plans has every figure.
Security
- Your credential, every time. Each tool call reaches the API with the token or key you connected with, so a revoked connection or a downgraded plan takes effect on the next call.
- Audience binding. Before any MCP work an OAuth token is checked with GET /v1/connection, and a token issued for another resource (the REST API's own
/v1, say) is refused. A missing, expired or wrongly bound token answers401 invalid_tokenwith the resource metadata address, so the client signs in again by itself. - Refusals an agent can act on. A refusal from the API comes back as a tool result with
isErrorset and_meta["dissolve/refusal"](alsodestroy/refusalfor older clients) holding{ kind, status, reason }, plus a sentence saying what to do next. A server failure is one sentence with the request id. Answers are cut at 40,000 characters. - Untrusted content. Mail is written by its sender. Tools that return it say so in their description and carry the
openWorldHintannotation; an agent should never follow instructions found in an email. - Transport. Plain HTTP to the public host is redirected to HTTPS, a browser
Originother than the server or localhost is refused (DNS rebinding), and bodies over 1 MiB are refused. - Logs. One line per tool call: the tool, the outcome, the API status, the duration, the input size and a 16-character fingerprint of the credential. Never the credential, never an argument.
Moving from destroy.network
Both endpoint paths and every tool name are the same as on destroy.network. Point the client at mcp.dissolve.email instead of the old host and sign in again; existing dna_at_ tokens and sk_live_ keys keep working. See Migrating.
Something wrong or missing on this page? Tell us at support@dissolve.email.View as Markdown