SendGrid MCP connector
The SendGrid connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent manage SendGrid teammates, API keys, alerts, and scheduled sends in plain language, with every action running inside the connecting person's permissions and recorded in an audit log.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect SendGrid to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect SendGrid once
-
Open Connections, choose Add connection, and pick SendGrid.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a SendGrid API key. One person generates a token in SendGrid and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect SendGrid to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect SendGrid to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect SendGrid to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect SendGrid to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with SendGrid through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Onboard a new teammate in minutes
Invite a new hire to SendGrid and give them the same permissions as the rest of their team, all from one request. Check the pending invitation later and clear it if they never accepted.
-
Security
Rotate API keys before they go stale
List every SendGrid API key, spot the ones nobody recognizes, rename the ones that matter, and delete the rest. Ask for a summary of which keys were created this quarter before the next review.
-
Marketing
Check what is queued to send
Before a launch, ask what is sitting in SendGrid's scheduled sends so nothing goes out twice or on the wrong day.
-
Engineering
Set up alerts for usage and stats
Create a SendGrid alert that fires when email volume approaches the plan limit or when weekly stats are ready, and adjust the recipients when the on-call rotation changes.
-
Operations
Approve or clear access requests
See who has asked for more SendGrid access, approve the ones that make sense, and remove the ones that do not, without logging in to hunt for the queue.
-
Compliance
Audit who can touch email sending
Pull a list of every SendGrid teammate and subuser with what each one can do, then remove people who have moved on.
Try asking
- “List SendGrid teammates with admin access on the parent account.”
- “Which SendGrid API keys have not been used lately?”
- “Show pending SendGrid teammate invites older than two weeks.”
AI tools
SendGrid tools for your AI agents
275 tools are ready to call through Elaichi's MCP endpoint the moment you connect SendGrid, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting SendGrid gets you
6 screens from the product, each doing one job for your SendGrid account.
The agent
Ask about SendGrid teammates in plain language.
The agent reads live SendGrid teammates, subusers and API keys to answer.
- teammates
- api keys
- subusers
- pending teammates
Ask Elaichi to work across your apps.
List SendGrid teammates with admin access on the parent account.
Which SendGrid API keys have not been used lately?
Show pending SendGrid teammate invites older than two weeks.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach SendGrid.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
275 SendGrid tools are ready to call.
Teammates, pending invites, subusers and API keys covered without custom code.
- List all SendGrid teammates
- Get single SendGrid teammate by ID
- Create a SendGrid teammate
- Delete a SendGrid teammate by ID
Toolboxes
Each team gets its own SendGrid toolbox.
Curate one toolbox per team so support sees different SendGrid tools than ops.
- Lifecycle Marketing
- Support
- Platform Engineering
- Security
Shared connections
Share a SendGrid account, never the key.
See who connected each account and how many teams and members use it.
- Marketing EMEA
- Support
- Platform
- Security Review
Audit log
Every SendGrid call is written down.
When, who, what happened, type and resource for each teammate or key change.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs the SendGrid review for you.
Fetch teammates, group them, draft a digest, get approval, post back to SendGrid.
SendGrid digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch teammates
SendGrid
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
SendGrid
Queued
Collections and dashboards
SendGrid numbers land before anyone asks.
Four metrics, 14 days of teammates created and a team breakdown, refreshed hourly.
SendGrid health
Refreshed 4 minutes ago · every 15 minutes · from the teammates collection
Teammates
1,284 ↓ 12%
Api keys
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Teammates created
Last 14 days
By team
Share of activity
Marketing EMEA 34%
Support 27%
Platform 21%
Security Review 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect SendGrid to Claude?
In Elaichi, add SendGrid as a connector and paste in an API key from your SendGrid settings. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when prompted and SendGrid is available in the conversation.
Does SendGrid work with ChatGPT and Cursor as well as Claude?
Yes. Once SendGrid is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect SendGrid once and every client picks it up.
What can an AI agent actually do with my SendGrid account?
With SendGrid connected, an agent can list and invite teammates, change what a teammate is allowed to do, remove people, and clear pending invitations. It can list, create, rename, and delete API keys, set up and edit alerts, approve or reject access requests, and show what is waiting in scheduled sends. Because SendGrid exposes a lot of actions, short concrete asks such as "list all API keys created this month" work better than long paragraphs.
Does connecting SendGrid give the AI full access to my account?
No. Everything an agent does in SendGrid runs through the permissions of the API key that was connected and the Elaichi roles of the person who signed in. Elaichi can narrow that access further, for example to read only, but it can never grant more than the key already allows.
Can I stop an agent from deleting or changing things in SendGrid?
Yes. Restrictions in Elaichi apply per action, so you can allow listing SendGrid teammates and API keys while blocking deletion or edits. A blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt, accidental or otherwise, can reach it.
What happens to a SendGrid connection when someone leaves?
When a person is offboarded in Elaichi, their access to SendGrid through every AI client ends at once. A shared SendGrid connection keeps working for everyone else on the team. If you want to remove SendGrid entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Put SendGrid in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.