How do I install @sendraven/mcp?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does @sendraven/mcp need an API key?

No required environment variable is listed on this record.

What transport does @sendraven/mcp use?

@sendraven/mcp runs locally over stdio.

When was @sendraven/mcp last checked?

Last checked 2026-10-28. MCP server for SendRaven, email infrastructure for AI agents: send email, read replies as threads, run campaigns and automations, with per-key limits and approvals.

Server MCP @sendraven/mcp

Power your agent

Tambahkan server ini

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Jalankan di PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @sendraven/[email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add sendraven-mcp -- npx -y @sendraven/mcp@0.4.25

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "sendraven-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "@sendraven/[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Jalankan di PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Buka

Server facts

Local

Transport: stdio
Version: 0.4.25
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

@sendraven/mcp

The SendRaven MCP server. Send email, read replies as threads, run campaigns and automations, and decide approvals, from any client that speaks the Model Context Protocol.

SendRaven is email infrastructure for AI agents. Agents use it over REST or MCP to run real email conversations: sending, reading replies as threads, and running campaigns and automations, within limits and approvals set on the API key. It is priced per email sent, never per contact.

Install

Claude Code, remote server, signs in with OAuth on first use:

claude mcp add --transport http sendraven https://mcp.sendraven.ai/mcp

Cursor, Claude Desktop, and other clients with a JSON config:

{
  "mcpServers": {
    "sendraven": {
      "url": "https://mcp.sendraven.ai/mcp"
    }
  }
}

Any client, as a local process. Create an API key under Developers in the dashboard, then:

claude mcp add sendraven -e SENDRAVEN_API_KEY=sk_live_… -- npx -y @sendraven/mcp

{
  "mcpServers": {
    "sendraven": {
      "command": "npx",
      "args": ["-y", "@sendraven/mcp"],
      "env": { "SENDRAVEN_API_KEY": "sk_live_…" }
    }
  }
}

Remote server with a key instead of OAuth, for an agent running unattended:

{
  "mcpServers": {
    "sendraven": {
      "url": "https://mcp.sendraven.ai/mcp",
      "headers": { "Authorization": "Bearer sk_live_…" }
    }
  }
}

Give an agent's key a daily send limit, a recipient allowlist, or an approval hold. The tools respect all three, campaigns included: a key with an approval hold or an allowlist cannot start a campaign, and a key with a daily limit can start one only if its recipients fit what is left of the day. See Limits for agents.

Behaviour worth knowing

A held send is not a failure. When a key requires approval, send_email returns pending_approval with an id. Report that it awaits a person; do not retry.
Out of plan is 402, not 429. get_usage reports plan, usage and remaining, so an agent can say "you are near your limit" before a batch.
Two calls cannot be undone. send_broadcast mails an audience; run preview_broadcast first. remove_suppression lets us mail an address that bounced or complained. Neither is a way to fix a failed send.
Approvals are decided by a person. decide_approval answers 403 when the client signed in with OAuth, when the key drafted the message, and when the key has any guardrail. Use the dashboard, or a key without guardrails.
Retry sends with the same idempotency_key, and only for the identical message. A retry replays the first answer instead of sending twice; the same key with different arguments is refused with idempotency_key_reused and nothing is sent.
A failed call returns the API's own message with its HTTP status and error type, so "No verified transactional sending domain for …" comes back as those words with HTTP 422 no_verified_identity, and a missing template variable lists the names in missing. Types mean the same thing on every tool; see Errors.

Tools

56 tools, generated from the server's registry.

Tool	What it does
`send_email`	Send a transactional email, immediately or scheduled. scheduled_at takes a relative phrase like 'in 3 days' or an ISO timestamp. The From domain must already be verified. Every accepted send answers with the same fields: id, status, thread_id, scheduled_at, skipped, reason and approval_id. skipped: true (status 'rejected', with reason) means every recipient was suppressed or opted out and nothing was sent; a retry answers the same. status 'pending_approval' (with approval_id) means a person must release it; a retry does not release it. Otherwise skipped is false and reason and approval_id are null. idempotency_key makes a retry of the identical message safe; it matches only the identical message. Refusals, by type: 422 no_verified_identity (the From domain has no verified sending domain; a retry answers the same until it is added and verified); 422 invalid_request (a bad field, or more than 50 recipients across to, cc and bcc, which fit as separate messages or a campaign); 422 unknown_topic; 422 invalid_schedule; 403 recipient_not_allowed (this key's allowlist); 429 daily_limit (this key's daily cap; it resets tomorrow, and a retry today answers the same); four billing refusals, all 402 and none retryable — plan_limit_reached (the Free plan's 3,000 emails a month are spent; a person has to activate paid sending), payment_method_required (the workspace has never had a payment method verified, so no outbound email leaves it at all, including on Free; only a person can add one, in the dashboard), billing_past_due (the payment failed for good) and budget_exceeded (the workspace's own spend ceiling; by default it stops marketing and lets transactional through); 422 workspace_suspended and 422 no_postal_address (a person has to act). 502 ses_error is the provider, and a later retry with the same idempotency_key is safe. get_usage shows which of these applies before a send, and apart from ses_error none clears by repeating the call.
`list_emails`	List messages newest first with their delivery status, including held, scheduled, skipped and failed ones and the mail campaigns and automations sent. Filter by status, recipient or tag. Paged: at most 100 per call; while has_more is true, next_cursor passed back as cursor with the same filters returns the next page. An unknown status is refused with 422 invalid_request rather than answering an empty log.
`get_email`	Fetch one message with its full event timeline (send, delivery, bounce, complaint, open, click). The timeline shows why an email didn't arrive.
`cancel_scheduled_email`	Cancel a scheduled email before it sends. Only works while status is 'scheduled': a message that has already started sending, or is in any other state, answers 409 invalid_state naming its status; a retry answers the same, and get_email shows where it stands. An unknown id answers 404 not_found.

Environment

Variable	Purpose
`SENDRAVEN_API_KEY`	Bearer key for the local process. Not needed for the remote server with OAuth.
`SENDRAVEN_API_URL`	Defaults to `https://api.sendraven.ai`.
`PORT`	When set, the server listens over Streamable HTTP instead of stdio.

The server holds no database or provider credentials of its own. It is a proxy over the public REST API and can reach exactly what the caller's key can reach.

@sendraven/mcp

Tambahkan server ini

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install @sendraven/mcp?

Does @sendraven/mcp need an API key?

What transport does @sendraven/mcp use?

When was @sendraven/mcp last checked?

Documentation

@sendraven/mcp

Install

Behaviour worth knowing

Tools

Environment

Links

License