Add Samva to Cursor

Cursor connects to Samva's hosted MCP server at https://mcp.samva.dev and signs in with OAuth. Once connected, Cursor's agent can check your sending setup, send and read email, and work a mailbox, inside the one organization you approve.

Add the serverCopy Anchor Link

Add the server to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json to use it in every project:

{
  "mcpServers": {
    "samva": {
      "type": "http",
      "url": "https://mcp.samva.dev",
      "auth": {
        "CLIENT_ID": "samva-cursor-plugin",
        "scopes": ["openid", "profile", "email", "offline_access"]
      }
    }
  }
}

The auth block names Samva's public OAuth client for Cursor. It is not a secret. Cursor needs it to sign in, because Samva does not accept clients that register themselves at sign-in.

Cursor lists the server but does not load it until you approve it. From a terminal, cursor-agent mcp list shows samva: not loaded (needs approval). Approve it in Cursor's MCP settings, or run:

cursor-agent mcp enable samva

Connect your accountCopy Anchor Link

Connect the server from Cursor's MCP settings, or run:

cursor-agent mcp login samva

The browser opens Samva's authorization page. It names the client, shows where the browser returns to, and lists your organizations. Choose one organization and select Authorize. The connection acts as you, with your role in that organization, as Connect an agent over MCP describes. Leave Whole organization selected for the first check below: a connection confined to a namespace cannot read the organization's profile or readiness.

Cursor reports MCP login successful, cursor-agent mcp list shows samva: ready, and cursor-agent mcp list-tools samva lists the tools the connection can call.

Run a first checkCopy Anchor Link

Start with a prompt that only reads:

Using Samva, check whether this organization is ready to send email and list what is left to set up.

The agent calls profile_get to name the organization and email_check_readiness to report whether it can send. Neither tool sends email. Tools that send, schedule, publish, or change settings are writes, so ask for them only when you mean them.

Hold mailbox sends for approvalCopy Anchor Link

Decision rules apply to mailbox actions. A send from a mailbox, an agent reply, or an integration tool call goes out, waits for a person, or is refused according to the organization's, the mailbox's, and the actor's rules. A held send returns as waiting for approval and goes out only when someone approves it. See Review mailbox actions.

Those rules do not cover messages_send_email, which sends as soon as the agent calls it. To keep a person in the loop for that tool, set your client to ask before it runs.

TroubleshootingCopy Anchor Link