Skip to main content
eCardWidget

Model Context Protocol server

The eCardWidget MCP Server: Send eCards from Claude, Cursor & AI Agents

Connect any MCP-compatible AI assistant to your eCardWidget account with an API key you generate and scope yourself. Ask in plain language — your assistant sends eCards, builds widgets, runs campaigns, and manages your team directory.

Add to your assistant Read the setup guide
$ npx -y ecardwidget-mcp
22 tools 4 guided flows Works with Claude, Cursor & any MCP client Free & open source (MIT)

One key, your whole account

Agentic AI automation for eCards — everything you'd do in the dashboard, by asking

Your AI assistant works through the same REST API your integrations use, scoped to exactly what your key allows. Use it to send digital greeting cards one at a time, run bulk eCard campaigns, or keep team recognition eCards flowing on autopilot.

Send & schedule eCards

Send, schedule, or share any eCard by email or link — one recipient or your whole directory. ecw_send_ecard

Design cards & widgets

Create widgets and eCard designs from scratch — image by URL or upload. ecw_create_widget

Run bulk campaigns

Draft a bulk eCard send, attach cards and recipients, review, then send. ecw_create_campaign

Recurring automations

Stand up automated birthday eCards, work anniversary eCards, and onboarding auto-sends. ecw_create_automation

Manage your directory

Import and update the team members your cards and automations target. ecw_import_team_members

Self-describing tools

The server asks the API what your key can do and which fields to set — no guessing. ecw_describe_fields

Set up in a minute

Three ways to connect your AI assistant

Same server, different names: Claude Desktop installs it as an extension, claude.ai calls these connectors, and ChatGPT’s connectors speak MCP too.

First, generate a scoped API key at Settings → Developers → API Keys. Then pick your client.

One click

CLAUDE DESKTOP

Install the Claude Desktop Extension

Download the Desktop Extension (.mcpb bundle) below and open it — Claude Desktop asks for your API key and stores it in your OS keychain.

Download the .mcpb release
→ open it → paste key
Download the extension Step-by-step guide →
Any client

CLAUDE CODE · CURSOR

Sign in once

Run login once to save your key locally, then add the server with no key in the command.

npx ecardwidget-mcp login
claude mcp add ecardwidget \
  -- npx -y ecardwidget-mcp

Step-by-step guide →  ·  View on npm →

Manual

CONFIG FILE

Add to mcpServers

Drop this into your client's MCP config with your key in the environment.

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

Full config reference →

Full instructions, tool reference, and troubleshooting in the AI Assistants (MCP) guide.

Built to be trusted

It can only ever do what your key allows

Scope enforcement, rate limiting, and audit logging happen on our servers — not in the AI client.

Scoped by construction

Grant view, manage, or no access per area. The assistant only sees the tools your key permits — anything out of scope is refused.

Two-step confirmation

Deletes and campaign sends require a preview plus a one-time token before anything happens. Nothing sends on a whim.

Your key stays yours

Stored in your OS keychain (desktop) or your own environment. Never logged, never sent anywhere but eCardWidget.

Fully audited & rate-limited

Every action is logged and each key is throttled — the same protections as any eCardWidget API call.

Guided flows

Automate greeting cards with AI — start from a prompt

Built-in flow templates walk the assistant through multi-step jobs — the agentic-automation version of a setup wizard.

/run_campaign

Draft a bulk send, attach cards and recipients, review, then send.

/setup_automation

Stand up a recurring birthday, anniversary, or onboarding send.

/spin_up_widget

Create a widget and add eCards to it in one guided pass.

/import_directory

Bulk-import the people your cards and automations target.

Questions

What to know before you connect

What is the eCardWidget MCP server?

It's an official server for the Model Context Protocol (MCP) — the open standard AI assistants use to connect to external tools. It lets an assistant like Claude operate your eCardWidget account: sending eCards, building widgets, running campaigns and automations, and managing your team directory, all authenticated by an API key you control.

Which AI clients does it work with?

Any MCP-compatible client — including Claude Desktop, Claude Code, and Cursor. Claude Desktop offers a one-click install; other clients add it with a short command or a config entry. See the setup guide for client-specific steps.

Is it secure? Can the AI do anything it wants?

No. The assistant can only use the areas your API key is scoped for, and the server enforces that regardless of what the client requests. Destructive actions require a two-step confirmation, your key is stored in your OS keychain, and every action is logged and rate-limited.

Is this the same as a Claude extension or connector?

Yes — they're different names for the same MCP standard. Claude Desktop packages MCP servers as one-click Desktop Extensions (.mcpb bundles), claude.ai lists MCP integrations as connectors, and ChatGPT's connectors are built on MCP as well. However your client names it, the eCardWidget server underneath is identical: the same 22 tools, the same scoped API key.

What is agentic AI, and how does this use it?

Agentic AI means an assistant that doesn't just answer questions — it takes multi-step actions on your behalf using tools. The eCardWidget MCP server is agentic automation applied to greetings and recognition: you state the goal ("send anniversary cards to everyone hitting 5 years this quarter") and the assistant plans the steps, calls the right tools, previews the result, and executes once you confirm.

Can I send AI eCards — have Claude send eCards for me?

Yes — that's exactly what this is for. Once connected, you can send eCards with AI in one sentence: "send a get-well card to Sam," "schedule holiday cards for every client," or "set up automated birthday eCards for the team." The assistant picks the design, personalizes the message, previews it, and sends through your eCardWidget account.

How much does it cost?

The MCP server is free and open source (MIT). It works with your existing eCardWidget account and API key — normal plan limits apply to what you send.

Where do I get an API key?

In your eCardWidget dashboard under Settings → Developers → API Keys. Generate a key, choose its permissions, and paste it in when your client asks. You can revoke or re-scope it anytime.

Ready when you are

Give your assistant the keys

Generate a scoped API key, add the server to your client, and start sending eCards from your AI assistant in minutes.

Get your API key View on GitHub

Also see: MCP setup guide · API documentation · AI Agents & LLMs hub · Zapier integration