Renply MCP for Cursor and agents

Test keys only. No live production authority, send, or publish.

Renply is the transactional email framework for developers. The stdio MCP server lets Cursor (and other agents) call render and validate without a live key.

30-second setup

  1. Create a test API key in the dashboard (never a live key).
  2. From Bytelon/renply-mcp: go build -o renply-mcp ./cmd/renply-mcp and put the binary on your PATH.
  3. Add to Cursor mcp.json:
{
  "mcpServers": {
    "renply": {
      "command": "renply-mcp",
      "env": {
        "RENPLY_API_KEY": "renply_test_…",
        "RENPLY_BASE_URL": "https://api.staging.renply.com/v1"
      }
    }
  }
}

A test key is enough for auth_key, render, and validate. Default scopes: templates.read,render,validate. Writes are opt-in and still need confirm: true.

There is no send or publish tool. Live keys (renply_live_) are refused. Threat model: THREAT-MODEL-MCP.

Sign upLog inGitHubTrust Center