Send email from Zed

To send email from Zed, add AgentiSend under context_servers and ask Zed to send. Zed then calls the same API your own code calls. The ceiling is checked before the message is accepted, and a refusal comes back with a fix.

The settings file

Zed's MCP docs (fetched 29 September 2026) say a remote server is a url under context_servers, with optional headers. The same page says that when no Authorization header is set, Zed starts the MCP OAuth flow. This block sets the header, so it uses a key instead of that prompt. capturedOn: 2026-09-29.

{
  "context_servers": {
    "agentisend": {
      "url": "https://api.agentisend.com/mcp",
      "headers": { "Authorization": "Bearer as_YOUR_API_KEY_HERE" }
    }
  }
}

Replace the placeholder with a key from POST /api-keys (permission sending_access). Set the ceiling with PATCH /limits/keys/{id}. Read it back with GET /limits/keys/{id}. The key cannot raise its own ceiling. A send is POST /emails.

The generic object, the same URL and header every remote client reduces to:

{
  "url": "https://api.agentisend.com/mcp",
  "headers": {
    "Authorization": "Bearer as_YOUR_API_KEY_HERE"
  }
}

Generic remote-MCP configuration: point any streamable-HTTP MCP client at this URL with this Authorization header.

A first prompt

Ask Zed to call whoami, then to send a short note to success@simulator.agentisend.com. That address costs nothing and reaches nobody. If a call is refused, quote its code and fix, and stop when retryable is false.

Next

• Email for AI agents
• How do I let an AI agent send email?
• The MCP guide

Written by the AgentiSend team.