Connect Cursor to Postal

Check these points before opening the Cursor setup. They prevent most connection failures.

• A team with the "MCP server" plan feature (mcp_access); without it the server responds 403 plan_limit_reached.
• To send emails, the team needs at least one verified domain.
• If you will use an API key: create the key in the dashboard, under API keys. It starts with ps_; a send-only key is enough if you will only send.
• Each connection acts on a single team. To use another team, connect again and pick the other one.
• Connections are listed under Settings › AI connections in the dashboard, where they can be revoked at any time.

Follow the steps in order. The server address is always https://api.postal.so/mcp. Recommended path: sign in with your account (OAuth). The API key is the alternative.

1. 1

   Create (or edit) the project's .cursor/mcp.json file, or ~/.cursor/mcp.json to apply to all projects.

2. 2

   Paste the configuration below. Only the URL is needed: Cursor registers itself (Dynamic Client Registration) and opens the Postal OAuth login.

3. 3

   On the Postal screen, choose the team and click Allow. Cursor stores and renews the tokens on its own.

4. 4

   To use an API key instead of OAuth, use the second configuration and set POSTAL_API_KEY in the environment that starts Cursor.

{
  "mcpServers": {
    "postal": {
      "url": "https://api.postal.so/mcp"
    }
  }
}

{
  "mcpServers": {
    "postal": {
      "url": "https://api.postal.so/mcp",
      "headers": {
        "Authorization": "Bearer ${env:POSTAL_API_KEY}"
      }
    }
  }
}

cursor://anysphere.cursor-deeplink/mcp/install?name=postal&config=eyJ1cmwiOiJodHRwczovL2FwaS5wb3N0YWwuc28vbWNwIn0=

Postal splits access into three levels, explained in the scopes table. For Cursor:

The simplest proof is to ask for something read-only inside Cursor itself. The connection also shows up under Settings › AI connections in the Postal dashboard, with the app, the team and the last use.

For those who want the technical proof

npx @modelcontextprotocol/inspector --cli https://api.postal.so/mcp \
  --transport http \
  --header "Authorization: Bearer ps_..." \
  --method tools/list

The Inspector proves that the Postal server responds. It does not test Cursor itself. The full walkthrough is in Validate the connection.

Go through the list in order. Then read what we know (and what we don't know) about Cursor.

What was tested and what was not