How to connect SendGrid and Mailgun to Cursor

Checked against Cursor's documentation on Oct 26, 2026. Commands and config blocks are generated from the same install data as each listing page.

1. 1. Check what you need

   Cursor only has to reach api.sessy.do over the network. No local program is involved.

   • It needs Authorization (next step).

2. 2. Get Authorization

   Authorization is the only value to collect. Get it before you edit config so you can export it right away.

   • Authorization (required): Bearer token from your Sessy API keys page (https://app.sessy.do/api_keys). Self-hosters: point the URL at your own instance's /mcp endpoint instead of api.sessy.do. Setup: https://sessy.do/docs/mcp.

3. 3. Add Sessy — Amazon SES observability to Cursor

   The entry holds an address and an Authorization header that points at SESSY_TOKEN. The export below supplies the value.

   {
     "mcpServers": {
       "sessy": {
         "url": "https://api.sessy.do/mcp",
         "headers": {
           "Authorization": "${env:SESSY_TOKEN}"
         }
       }
     }
   }

   Copy

   export SESSY_TOKEN="Bearer paste-your-token-here"

   Copy

   • Cursor expands ${env:NAME} from its own environment, so the variable has to be set where Cursor starts.

4. 4. Restart or reload if it does not appear

   Missing from the list? This step records what the Cursor docs say about restarts and about tool approval.

   • The docs do not say whether editing mcp.json needs a restart. They tell you to restart Cursor after updating files of a custom local server.
   • Cursor asks for approval before an agent uses an MCP tool unless you allowlist it.