Sidemail

Created By
Sidemail10 months ago
Sidemail.io's official MCP Server. Provides Model Context Protocol (MCP) integration for Sidemail.io, enabling programmatic access to Sidemail's transactional emails, contacts, domains, and Messenger features for product updates and newsletters via MCP agent mode (in VS Code, Claude, Cursor and other MCP clients).
Overview

What is Sidemail

Sidemail is an all-in-one email delivery platform. It covers everything for delivering and managing emails – transactional emails, email marketing, email automation, contact profiles management, and subscribe forms.

What is Sidemail MCP Server

Sidemail MCP Server provides Model Context Protocol (MCP) integration for Sidemail.io, enabling programmatic access to Sidemail's transactional email, contacts, domains, and Messenger features for product updates and newsletters via MCP agent mode (in VS Code, Claude, Cursor, and other MCP clients).

Key features

  • Manage sending domains
  • Test sending transactional emails
  • Manage contacts and groups
  • Create, update, and delete Messenger drafts
  • Query sent emails and contacts

Prerequisites

  • Node.js v18 or newer
  • Sidemail API Key

Claude Desktop setup

Edit (or create) the config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json
{
	"mcpServers": {
		"sidemail": {
			"command": "npx",
			"args": ["-y", "@sidemail/mcp"],
			"env": { "SIDEMAIL_API_KEY": "your-key" }
		}
	}
}

Microsoft VS Code setup (assisted)

  1. Open the Command Palette (Ctrl/Cmd + Shift + P).
  2. Type “MCP: Add Server…” and select it.
  3. Select "NPM Package".
  4. Enter @sidemail/mcp and confirm it.
  5. Confirm the installation.
  6. Enter your Sidemail API key and confirm it.

Microsoft VS Code setup (manual)

Alternatively, you can install it manually by modifying the mcp.json configuration file.

  1. Open the Command Palette (Ctrl/Cmd + Shift + P).
  2. Type “MCP: Open User Configuration” and select it.
  3. Add the configuration below and save changes.
{
	"servers": {
		"sidemail-mcp": {
			"type": "stdio",
			"command": "npx",
			"args": ["-y", "@sidemail/mcp"],
			"env": {
				"SIDEMAIL_API_KEY": "${input:sidemail-key}",
			},
		},
	},
	"inputs": [
		{
			"type": "promptString",
			"id": "sidemail-key",
			"description": "Sidemail API Key",
			"password": true,
		},
	],
}

Cursor setup

Create or edit ~/.cursor/mcp.json:

{
	"mcpServers": {
		"sidemail": {
			"command": "npx",
			"args": ["-y", "@sidemail/mcp"],
			"env": { "SIDEMAIL_API_KEY": "your-key" }
		}
	}
}

CLI Usage

npx @sidemail/mcp

MCP Server Tools

Domains

  • list-domains: List all sending domains
  • create-domain: Add a new sending domain
  • delete-domain: Remove a sending domain

Messenger

  • list-messenger-drafts: List Messenger drafts
  • get-messenger-draft: Get Messenger draft by ID
  • create-messenger-draft: Create a Messenger draft
  • update-messenger-draft: Update a Messenger draft
  • delete-messenger-draft: Delete a Messenger draft

Groups

  • list-groups: List all contact groups
  • create-group: Create a new contact group
  • update-group: Update a contact group

Contacts

  • create-or-update-contact: Create or update a contact
  • query-contacts: Query contacts with filters
  • find-contact: Find a contact by email
  • delete-contact: Delete a contact

Emails

  • send-email: Send a transactional email (testing only)
  • query-emails: Query sent emails

Server Config

{
  "mcpServers": {
    "sidemail": {
      "command": "npx",
      "args": [
        "-y",
        "@sidemail/mcp"
      ],
      "env": {
        "SIDEMAIL_API_KEY": "your-key"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
Sidemail
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

7 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago