sendgrid

The SendGrid MCP Server exposes SendGrid API v3 capabilities through the MCP (Model Context Protocol) interface, giving you programmatic access to a wide range of email management, automation, templates, analytics, and sender identity tools. With 59 tools available, you can perform actions such as creating and managing contact lists, sending transactional or marketing emails, handling dynamic templates with Handlebars, managing suppressions, and analyzing performance data across multiple dimensions. To use it, install and run the server, then configure your MCP client to point to the server name (for example, sendgrid) and provide your API key via environment variables. The server supports read-only mode by default, ensuring a safe environment where mutating operations are blocked while still providing access to analytics and listing capabilities. Tools are available through your MCP client’s interface once the server is registered.

Prerequisites:

• Node.js and npm installed on your machine
• Access to a SendGrid API key (SG...)

Step-by-step installation:

1. Install the MCP server globally via npm: npm install -g sendgrid-mcp

2. Obtain a SendGrid API key from the SendGrid dashboard (API Keys) and store it securely.

3. (Optional) Verify the installation by listing the server in your MCP client configuration:

   • Create or update your MCP client config to include the SendGrid MCP server (see configuration examples in the README).

4. Start using the server by configuring your MCP client to reference the SendGrid MCP server. Example environment variables may include SENDGRID_API_KEY and READ_ONLY. You can also run locally from a built path if building from source: npm run build node /absolute/path/to/sendgrid-mcp/build/index.js

5. If you’re integrating with a specific MCP client, follow that client’s steps to add a new MCP server and point it to the SendGrid MCP server with the appropriate environment variables.

Tips and notes:

• Environment variables: SENDGRID_API_KEY is required. READ_ONLY defaults to true for safety; set to false to enable write operations. Other optional vars include LOG_LEVEL and REQUEST_TIMEOUT.
• Read-only mode: In READ_ONLY=true, all tools are registered and visible, but mutating operations (create, update, delete) are blocked with a clear error message. This is ideal for safe exploration and analytics access.
• If you encounter authentication errors, double-check your SENDGRID_API_KEY and that it has sufficient permissions.
• For local testing, you can run the server via node with a built path to a built index.js and provide the necessary env vars as shown in the README’s examples.
• The server is designed to work with a variety of MCP clients (Claude Desktop, Claude Code, Cline, Zed Editor, Continue, and generic MCP clients). Ensure your client configuration aligns with the sample JSON templates provided in the README.