Skip to content
CommunicationQuality Score: 46

Email Activity (beta) MCP Configuration

The Email Activity (beta) MCP configuration provides a hosted JSON schema that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Email Activity (beta) API via the Model Context Protocol. This configuration maps 10 API endpoints as callable tools, including Retrieve all recent access attempts, Retrieve a list of currently allowed IPs, Add one or more IPs to the allow list, and more. No authentication credentials are needed — it works out of the box. The configuration is auto-generated from the Email Activity (beta) OpenAPI specification (v1.0.0) and has a quality score of 46/99 (fair documentation coverage). Use the hosted URL below to auto-load this schema into any compatible MCP client.

Quick Specs Reference

AuthenticationNo Auth Required
Available Endpoints10 tools mapped
Integration Modeauto Generation

Hosted Config URL

Use this hosted URL in any client that supports remote MCP schema auto-loading.

https://mcpbridge.org/config/sendgrid-com.json

One-Click Client Setup

Copy the configurations below to wire your local coding assistant directly.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "sendgrid-com": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp/sendgrid-com"
      ],
      "env": {
        "EMAIL_ACTIVITY__BETA__API_KEY": "your_email_activity__beta__api_key"
      }
    }
  }
}

Cursor & VS Code

MCP Server URL Setup
{
  "mcpServers": {
    "sendgrid-com": {
      "url": "https://mcpbridge.org/config/sendgrid-com.json"
    }
  }
}

Raw Configuration JSON

For local command line wrappers or dynamic shell bindings.

{
  "mcpServers": {
    "sendgrid-com": {
      "command": "npx",
      "args": ["-y","@mcp/sendgrid-com"],
      "env": {
      "EMAIL_ACTIVITY__BETA__API_KEY": "your_email_activity__beta__api_key"
}
    }
  }
}

Required Environment Keys

Substitute these secrets inside your configuration directory environment definitions.

EMAIL_ACTIVITY__BETA__API_KEY
Replace your_email_activity__beta__api_key with your secret key credential

Mapped Web APIs & Tools

The following routes will be exposed directly as protocol tools for the LLM.

GET/access_settings/activity

Retrieve all recent access attempts

GET/access_settings/whitelist

Retrieve a list of currently allowed IPs

POST/access_settings/whitelist

Add one or more IPs to the allow list

DELETE/access_settings/whitelist

Remove one or more IPs from the allow list

GET/access_settings/whitelist/{rule_id}

Retrieve a specific allowed IP

DELETE/access_settings/whitelist/{rule_id}

Remove a specific IP from the allowed list

GET/alerts

Retrieve all alerts

POST/alerts

Create a new Alert

GET/alerts/{alert_id}

Retrieve a specific alert

DELETE/alerts/{alert_id}

Delete an alert

Similar Configurations

Slack API

Send messages, manage channels, and integrate Slack notifications into your AI agent workflows.

https://mcpbridge.org/config/slack.json

Discord API

Send messages, manage servers, and integrate Discord bots into your AI agent workflows.

https://mcpbridge.org/config/discord.json

Twilio API

Send SMS, make calls, and manage communication channels through your AI agent.

https://mcpbridge.org/config/twilio.json

Adafruit IO REST API

Adafruit IO is a cloud platform developed by Adafruit Industries, specifically designed to serve as the backbone for the Internet of Things for everyone. Its core HTTP REST API provides a universal interface for interacting with time-series data streams known as "feeds," which represent data points from sensors or commands to actuators. The API enables developers to retrieve, create, and manage data, dashboards, and webhooks, effectively abstracting the complexity of raw data ingestion and visualization. Typical use cases span from consumer hobbyists building home automation systems and weather stations to enterprises prototyping industrial monitoring solutions, asset tracking, and automated alerts. The platform’s strength lies in its simplicity and accessibility, allowing data from any HTTP-capable device—from a Raspberry Pi to an industrial PLC—to be logged, visualized, and acted upon without managing backend infrastructure. When this API is exposed as a set of tools to an AI coding assistant via the Model Context Protocol (MCP), it transforms the assistant from a mere code generator into an active IoT operations agent. The AI can directly interact with the live Adafruit IO environment, bridging the gap between developer intent and runtime data manipulation. This integration unlocks significant value by enabling context-aware automation; the AI can understand the current state of feeds and dashboards to suggest or implement improvements, debug connectivity issues by checking recent activities, or dynamically adjust configurations based on real-world data patterns. For a developer, this means the AI can not only write the client code but also test it, verify data flow, and assist in the operational maintenance of the IoT solution within a single, seamless workflow. With MCP integration, a developer can instruct the AI to perform complex, multi-step tasks. For example, the AI agent can query a user’s activities to diagnose recent feed data ingestion failures, then automatically create a new webhook endpoint to re-establish a broken data pipeline. It can be instructed to retrieve the block layout of a specific dashboard, analyze its structure, and programmatically generate a new, optimized dashboard with updated blocks via the appropriate POST endpoints. Furthermore, the AI can fetch the status of all feeds under a username, identify any that are stale, and then craft the precise API calls needed to clean up obsolete data or notify the responsible systems, effectively automating routine data hygiene and monitoring tasks that would otherwise require manual console interaction or custom scripting. Critical to this integration is a clear understanding of authentication and security. Although the endpoint list specifies "None," the Adafruit IO API actually employs API key-based authentication, typically passed as a query parameter or an X-AIO-Key header. The provided "None" likely refers to no OAuth or complex token exchange; however, developers must treat their API keys as sensitive secrets, never hardcoding them in client-side code or committing them to version control. When configuring an MCP server, keys should be stored in environment variables or a secure vault. Adhering to the principle of least privilege is essential: generate and use separate, restricted API keys for AI agent access that have only the permissions required for its specific tasks—such as read-only access to certain feeds—rather than a master key with full account control. This confines any potential issues arising from AI-generated actions to a limited scope, safeguarding the integrity of the entire IoT ecosystem.

https://mcpbridge.org/config/adafruit-com.json