Ecardwidget MCP Server

eCardWidget MCP Server

The official Model Context Protocol server for eCardWidget. Let an AI assistant (Claude Desktop, Claude Code, Cursor, …) work in your eCardWidget account — search and send eCards, manage your directory, list campaigns/widgets/automations — using an API key you generate and scope yourself.

The assistant can only ever do what your API key permits. On startup the server asks the API what the key is allowed to do and registers only the tools that key is scoped for. All scope enforcement, throttling, and auditing happen server-side.

Quick start

First, generate a scoped API key in your eCardWidget dashboard: Settings → Developers → API Keys. Grant only the areas you want the assistant to touch. Then pick whichever install fits your client:

Option A — Claude Desktop (one click)

Download ecardwidget-mcp.mcpb from the latest release and open it. Claude Desktop shows an install dialog that asks you for your API key (stored in your OS keychain) — no config files, no commands.

Option B — Sign in once, then a short command (Claude Code / Cursor / any client)

npx ecardwidget-mcp login          # prompts for your key, verifies + saves it locally (0600)
claude mcp add ecardwidget -- npx -y ecardwidget-mcp   # no key in the command

The server reads the saved key automatically. (npx ecardwidget-mcp logout removes it.)

Option C — Put the key in your client config (manual)

{
  "mcpServers": {
    "ecardwidget": {
      "command": "npx",
      "args": ["-y", "ecardwidget-mcp"],
      "env": { "ECW_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Restart your client. It connects and shows the tools your key is scoped for. Precedence: an explicit ECW_API_KEY env var always wins over the saved login credential.

Configuration

Tools

All tools are namespaced ecw_*; only those your key is scoped for are registered.

• Introspection & discovery: ecw_whoami, ecw_describe_fields (what fields you can set on a widget / eCard / campaign / automation — synced from the OpenAPI spec)
• eCards: ecw_search_ecards, ecw_get_widget_ecards, ecw_create_ecard (image via URL or base64), ecw_send_ecard, ecw_delete_ecard
• Directory: ecw_list_team_members, ecw_find_team_member, ecw_upsert_team_member, ecw_import_team_members, ecw_deactivate_team_member, ecw_delete_team_member
• Widgets: ecw_list_widgets, ecw_create_widget, ecw_duplicate_widget, ecw_delete_widget
• Automations: ecw_list_automations, ecw_create_automation (birthday / anniversary / onboarding)
• Campaigns: ecw_list_campaigns, ecw_create_campaign (draft), ecw_send_campaign

Destructive tools (delete, send campaign) use a two-step confirmation — call once for a preview + a one-time token, then again with the token to execute. Deleting automations/campaigns and sending gift-card campaigns require confirmation in the dashboard.

Guided flows (prompts)

The server ships prompts — guided, multi-step flow templates your client surfaces as slash-commands/suggestions: run_campaign, setup_automation, spin_up_widget, import_directory (each shown only if your key is scoped for it). It also hands the assistant a compact overview of the object model and the core flows at connect, so it understands how widgets, eCards, campaigns, automations, and the directory fit together.

Ask naturally, e.g. "Send a birthday eCard from our Thank-You widget to grace@acme.com".

Security

See SECURITY.md. In short: least-privilege scoped keys, server-side enforcement is the real guarantee, destructive actions require a two-step confirmation, and the API key is never logged.

Development

npm install
npm run build          # tsup → dist/index.js
npm test               # vitest
npm run inspector      # MCP Inspector against the built server (needs ECW_API_KEY)

License

MIT