How-to

Connect other MCP clients

Add the hosted Emailit MCP server to VS Code, Windsurf, Zed or any client that supports remote Streamable HTTP servers, with OAuth or an API key.

Updated Oct 2, 2026

Any MCP client that supports remote servers over Streamable HTTP can use Emailit. Every client needs the same two things: the server URL and a way to authenticate.

Setting	Value
URL	`https://api.emailit.com/mcp`
Transport	Streamable HTTP (some clients call it `http` or `streamable-http`)
OAuth	Discovered from `https://api.emailit.com/.well-known/oauth-protected-resource/mcp`. Clients register with dynamic client registration or a client ID metadata document, and use PKCE.
API key alternative	Header `Authorization: Bearer your_api_key`
Options	`?toolsets=…` and `?read_only=true`, or the `X-MCP-Toolsets` and `X-MCP-Readonly` headers. See Toolsets.

The server is stateless: clients send JSON-RPC messages with POST and don’t need to keep a session.

Use OAuth when you work interactively: you choose the workspaces in the browser and no key is stored on disk. Use an API key for headless setups and for clients that don’t support MCP authorization.

VS Code

VS Code uses MCP servers in Copilot Chat’s agent mode. Add the server to .vscode/mcp.json in your workspace, or run MCP: Add Server from the Command Palette and choose HTTP:

.vscode/mcp.json

{
  "servers": {
    "emailit": {
      "type": "http",
      "url": "https://api.emailit.com/mcp"
    }
  }
}

Start the server from the MCP servers list and complete the Emailit sign-in in your browser.

Windsurf

Add the server in Windsurf’s MCP settings (the mcp_config.json file):

mcp_config.json

{
  "mcpServers": {
    "emailit": {
      "serverUrl": "https://api.emailit.com/mcp"
    }
  }
}

If your Windsurf version doesn’t support OAuth for remote servers, add an Authorization header with an API key instead.

Zed

Zed connects to remote servers through its context server settings. Add a server named emailit with the URL https://api.emailit.com/mcp and, if Zed doesn’t prompt you to sign in, an Authorization: Bearer your_api_key header. Check Zed’s documentation for the current settings format.

Any other client

Point the client at https://api.emailit.com/mcp. When it supports MCP authorization, it reads the discovery document, registers itself and opens the Emailit sign-in page. Otherwise send an API key:

mcp.json

{
  "mcpServers": {
    "emailit": {
      "url": "https://api.emailit.com/mcp",
      "headers": {
        "Authorization": "Bearer your_api_key"
      }
    }
  }
}

An API key connection works in the key’s workspace only, and lists only the tools the key’s scope allows: a Sending Only key exposes the email sending tools and nothing else.

Run it locally instead

For clients that only support stdio servers, use the open-source local server. It covers the original tool set; the hosted server has all 109 tools.