Available

SendGrid MCP server

SendGrid is a cloud email delivery service that sends transactional and marketing email at scale. Developers and marketing teams use it to reach inboxes reliably and track how messages perform. Connect through Arc0 to use the actions your identity is allowed to call.

EmailAPI keyMCP + RESTsendgrid.com
AUDIT LOG · SENDGRIDPOLICY: acme-support
09:41:07 · claude · u_8f2read
sendgrid.list_bounces
List bounces✓ allowed · 212ms
09:41:08 · claude · u_8f2read
sendgrid.get_bounce
Check one address for bounces✓ allowed · 164ms
09:41:09 · claude · u_8f2write
sendgrid.create_template
Create an empty transactional template✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
sendgrid.delete_bounce
Remove one bounce suppression✕ blocked · policy: deny
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT
01 · USE CASES

Agent workflows for SendGrid.

01

Send one email

Use when authorized to email the specified recipient now from a verified sender. Sends one plain-text email and consumes plan quota; acceptance is not delivery. Do not use for drafts or unsolicited outreach. On timeout check Email Activity or the owned mailbox before retrying.

02

List transactional templates

Use when discovering transactional template IDs and active versions. Returns structural metadata without subjects or message bodies. Pass next_page_token to continue; count is vendor metadata, not the number returned.

03

Get transactional template metadata

Use when checking a known transactional template ID and its active version before sending from another workflow. Returns structural metadata only; does not expose template subjects, HTML or personal content.

02 · ACTIONS

10 SendGrid actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

6

Look things up, subject to your permissions.

  • sendgrid.list_templates
    List transactional templates

    Use when discovering transactional template IDs and active versions. Returns structural metadata without subjects or message bodies. Pass next_page_token to continue; count is vendor metadata, not the number returned.

  • sendgrid.get_template
    Get transactional template metadata

    Use when checking a known transactional template ID and its active version before sending from another workflow. Returns structural metadata only; does not expose template subjects, HTML or personal content.

  • sendgrid.get_global_stats
    Get aggregate email statistics

    Use when assessing aggregate delivery, bounces, opens and clicks over a date range of up to 366 days. Contains no recipient-level data. Select day, week or month and use offset/limit for additional pages.

  • sendgrid.list_bounces
    List bounces

    Use when diagnosing undeliverable recipients. Returns a bounded page of addresses and structural status; no SMTP reason text. Contains personal data. Continue with offset plus limit; stop on an empty page.

  • sendgrid.list_spam_reports
    List spam reports

    Use when identifying recipient complaints to prevent further outreach. Returns a bounded page of addresses and structural status; no SMTP reason text. Contains personal data. Continue with offset plus limit; stop on an empty page.

  • sendgrid.get_bounce
    Check one address for bounces

    Use when checking whether one known consenting address has a bounce record. Returns structural timestamps and SMTP status without the address or reason text. Empty records mean no match; this does not prove that mail is deliverable.

write

2

Create and change things. Allow, or ask the user first.

  • sendgrid.send_mail
    Send one email

    Use when authorized to email the specified recipient now from a verified sender. Sends one plain-text email and consumes plan quota; acceptance is not delivery. Do not use for drafts or unsolicited outreach. On timeout check Email Activity or the owned mailbox before retrying.

  • sendgrid.create_template
    Create an empty transactional template

    Use when preparing a new transactional template container. Creates no version and sends no email. Do not use to edit an existing template. A timeout may still create it; inspect the template list before retrying.

destructive

2

Delete, cancel or archive. Ask first, or deny outright.

  • sendgrid.delete_template
    Delete a transactional template

    Use when explicitly authorized to permanently remove a known unused template and its versions. Sends no email but can break workflows using that ID. Do not delete an active production template. Read back after an unknown outcome before retrying.

  • sendgrid.delete_bounce
    Remove one bounce suppression

    Use when explicitly authorized to remove a resolved bounce for a consenting address. Permits future sends but sends no email itself. Do not use to bypass consent or unresolved delivery failures. After an unknown outcome, read the bounce before retrying.

03 · POLICIES AND AUDIT

Control access to SendGrid.

Connect the intended SendGrid account, authorize your AI client and set policies for its tools.

Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.

Configure policies and approvals

Example policy choices

  • Read actions: allow where authorized
  • sendgrid.create_template: require approval
  • sendgrid.delete_bounce: deny

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How SendGrid connects.

Connect SendGrid using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · AI CLIENTS

Use SendGrid with your AI client.

Sign in to Arc0 and connect SendGrid in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

SendGrid with Claude

Claude Desktop + Claude Code

  1. In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
SendGrid with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
SendGrid with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
SendGrid with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Cursor
SendGrid with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
SendGrid with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

After setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.

07 · FAQ

SendGrid and Arc0, answered.

Q01

Does SendGrid work with Claude Desktop and Claude Code?

Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.

Q02

Can I use SendGrid with OpenAI Codex, ChatGPT and Cursor?

Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.

Q03

Is this the official SendGrid MCP server?

This is Arc0’s integration page, not a claim of an official SendGrid server. Arc0 adds a shared connection, policy and audit experience across apps. Consult SendGrid for its own current MCP offerings.

Q04

Which SendGrid actions are supported?

10 registry-defined actions: 6 read, 2 write and 2 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.

Q05

Which permissions does SendGrid need?

Connect SendGrid using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

Q06

Can I restrict writes in SendGrid?

You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.

Q07

What does SendGrid through Arc0 cost?

See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.

Get started

Plug SendGrid into your agent.

SendGrid MCP server: 10 actions including send one email, list transactional templates, get transactional template metadata. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

SendGrid and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by SendGrid.