SendGrid MCP connector
The SendGrid connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects with an API key
- Free 14-day trial
- No credit card
List SendGrid teammates with admin access on the parent account.
Working in SendGrid with Elaichi
-
List all SendGrid teammates
-
Get single SendGrid teammate by ID
-
List all SendGrid API keys
How to connect SendGrid to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
SendGrid MCP connector for 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.
SendGrid MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
SendGrid MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
SendGrid MCP connector for 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.
SendGrid MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with SendGrid through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in SendGrid is logged.
-
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.”
What connecting SendGrid gets you
6 screens from Elaichi, each doing one job for your SendGrid account.
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, Cursor or Microsoft Copilot
The agent
Ask about SendGrid teammates in plain language.
The agent reads live SendGrid teammates, subusers and API keys to answer.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach SendGrid.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
275 SendGrid tools are ready to call.
Teammates, pending invites, subusers and API keys covered without custom code.
Toolboxes
Each team gets its own SendGrid toolbox.
Curate one toolbox per team so support sees different SendGrid tools than ops.
Shared connections
Share a SendGrid account, never the key.
See who connected each account and how many teams and members use it.
Audit log
Every SendGrid call is written down.
When, who, what happened, type and resource for each teammate or key change.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
SendGrid digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
SendGrid
Queued
Automations
A schedule runs the SendGrid review for you.
Fetch teammates, group them, draft a digest, get approval, post back to SendGrid.
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%
Collections and dashboards
SendGrid numbers land before anyone asks.
Four metrics, 14 days of teammates created and a team breakdown, refreshed hourly.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for SendGrid
All three can connect SendGrid to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over SendGrid tools | Allow or restrict single SendGrid tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per SendGrid call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deletion or edits. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client together.
Does the SendGrid MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. SendGrid is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for SendGrid?
Yes. Both let Claude, ChatGPT or Cursor use SendGrid. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every SendGrid call.
How is Elaichi different from Composio for SendGrid?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to SendGrid: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put SendGrid in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot