Skip to content

unitpostcom/unitpost

v1.0.0MIT

Your AI Agent sends the messages. Official Unitpost plugin: email and SMS infrastructure, run by your agent. Send transactional email and SMS, run campaigns, and manage contacts, templates, domains, and webhooks. Connects with OAuth 2.1 in the browser.

GitHubOpen Website

Unitpost plugin

Your AI Agent sends the messages. The official Unitpost plugin gives your agent email and SMS infrastructure: send transactional email and SMS, run campaigns, and manage contacts, templates, sending domains, and webhooks in your Unitpost workspace. It bundles Unitpost's hosted MCP server and the Unitpost skill, which teaches the agent the API and its send-safety rules.

Install

ClientHow
Claude Code/plugin marketplace add unitpostcom/unitpost-grok-plugin, then /plugin install unitpost@unitpost
Cursor (and Grok Bot)Cursor Marketplace → Unitpost
Grok BuildxAI plugin marketplace → Unitpost
Any MCP clientAdd https://mcp.unitpost.com/mcp as a remote (Streamable HTTP) server

Per-client guides: https://www.unitpost.com/docs/ai

Contents

  • .mcp.json / mcp.json — the remote MCP server https://mcp.unitpost.com/mcp (.mcp.json for Claude Code and Grok Build, mcp.json in the Agent Plugins format)
  • skills/unitpost/SKILL.md — when to use Unitpost and the send-safety rules
  • plugin.json (Agent Plugins), .claude-plugin/, .cursor-plugin/, .grok-plugin/ — manifests
  • assets/ — logo

Auth and safety

OAuth 2.1 in the browser: on first use your client opens Unitpost, you pick a workspace and approve the scopes. No credentials are stored in this plugin. Send tools are marked destructive, so your client asks before anything goes out. Email sends need a verified domain; SMS is on paid plans and enforces recipient consent and STOP opt-out.

Network endpoints called

  • https://mcp.unitpost.com/mcp (MCP)
  • https://www.unitpost.com/oauth/* (OAuth authorize/token)
  • https://www.unitpost.com/.well-known/oauth-* (discovery)

Links

Where this comes from

This repository is generated. Unitpost's CI publishes it from our main repository on every release, with a freshly built skills/unitpost/SKILL.md so the skill matches the live API. Each sync is a normal commit on top of the previous one, so any commit SHA pinned by a marketplace stays reachable. Pull requests here are overwritten by the next sync — email support@unitpost.com instead.