Developers · MCP

MCP tools for Mail Genie

Connect GenieOS MCP at https://mcp.genieos.pro/v1 and use email-scoped tools from Cursor, Claude, Codex, or any MCP 1.0 client.

Full MCP docs API · Templates

Email-scoped tools

list_templates
Browse workspace email templates.
create_template
Create a blank email template draft.
compose_template
Compose from a brief and persist as a draft.
read_template
Read template body, subject, and metadata.
render_template
Render preview HTML for a template key.
send_test
Send a test message to a verified address.
send_transactional
Send via POST /v1/templates/{key}/send.
list_sends
List recent sends with optional filters.
list_sequences
List published sequences (key, trigger, enrolment).
enroll_in_sequence
Enrol a contact in a named sequence.

Tool schemas, scopes, and every GenieOS MCP surface — pages, social, links — live in the complete Genie MCP docs.

install.mdmcp

# 1) Create a workspace API key#    app.genieos.pro → Developers → API keys (gos_…) # 2) Claude Code — flags before the server nameclaude mcp add --transport http \  --header "Authorization: Bearer gos_…" \  genieos https://mcp.genieos.pro/v1 # 3) Cursor — ~/.cursor/mcp.json (or Settings → Tools & MCP)# {#   "mcpServers": {#     "genieos": {#       "url": "https://mcp.genieos.pro/v1",#       "headers": { "Authorization": "Bearer gos_…" }#     }#   }# } # 4) Ask: "compose a welcome email" or "send transactional order_confirm"

Installation

Wire GenieOS MCP in three steps

Step 1
Get a GenieOS API key
Open the Developer Console, create a workspace key (gos_…), and copy it once. Live keys are on Glow+.
Open Developer Console →
Step 2
Point your MCP client at GenieOS
HTTP endpoint https://mcp.genieos.pro/v1 with Authorization: Bearer gos_… — or omit the header and complete OAuth on first tool call.
Step 3
Try a Mail Genie prompt
Ask your agent to list templates, compose from a brief with compose_template, or send a test with send_test / send_transactional.

Client configs

Cursor, Claude, Codex

Snippets below match the GenieOS docs. ChatGPT Developer Mode, Continue, Zed, and the stdio bridge are covered in the full guide.

Cursor

json

Edit ~/.cursor/mcp.json or use Settings → Tools & MCP → Add server. Restart Cursor; genieos appears under Tools & MCP.

{
  "mcpServers": {
    "genieos": {
      "url": "https://mcp.genieos.pro/v1",
      "headers": {
        "Authorization": "Bearer gos_…"
      }
    }
  }
}

Claude Code

bash

All flags go before the server name. Expect genieos · http · connected from claude mcp list.

claude mcp add --transport http \
  --header "Authorization: Bearer gos_…" \
  genieos https://mcp.genieos.pro/v1

claude mcp list

Claude Desktop

json

Claude Desktop speaks stdio — use the @genie-os/mcp bridge. Config path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows).

{
  "mcpServers": {
    "genieos": {
      "command": "npx",
      "args": ["-y", "@genie-os/mcp"],
      "env": {
        "GENIEOS_API_KEY": "gos_…"
      }
    }
  }
}

Codex

bash

Codex stores the env-var name, not the secret. Export GENIEOS_API_KEY in the shell that launches Codex.

export GENIEOS_API_KEY='gos_…'
codex mcp add genieos \
  --url https://mcp.genieos.pro/v1 \
  --bearer-token-env-var GENIEOS_API_KEY

codex mcp list

Need ChatGPT, Continue, Zed, or OAuth-only setup? See the complete Genie MCP documentation — including every tool schema beyond email.

Start free with Spark GenieOS MCP docs API · Templates Mail Genie API overview