eCardWidget MCP server
✓ VerifiedLets an AI assistant manage eCards, run bulk campaigns, and automate recurring cards through your eCardWidget account.
Also known as eCardWidget/ecardwidget-mcp
- Stars
- 1
- Tools
- 1
- Downloads, 30 days
- —
- Latest version
- 0.5.2
- Last commit
- Jul 9, 2026
- License
- MIT
What is eCardWidget MCP?
eCardWidget lets an AI assistant manage eCards, run bulk campaigns, and automate recurring cards through your eCardWidget account. It exposes 1 tool, such as eCards.
Summary generated from the project's README
About eCardWidget MCP server
Managing digital greetings and recipient directories through an AI assistant is what this server enables for eCardWidget users. By connecting to clients like Claude Desktop, Claude Code, or Cursor, you can instruct an AI to handle tasks such as searching for specific eCards, creating new widgets, or managing team member directories. The server uses a scoped API key generated in your dashboard to ensure the assistant only accesses permitted areas of your account.
Setup involves either using a one-click installer for Claude Desktop or running an npx login command for other clients. The server dynamically registers tools based on your key's permissions, including ecw_search_ecards, ecw_create_automation, and ecw_list_campaigns. To prevent accidental errors, destructive actions like sending a campaign or deleting an eCard require a two-step confirmation process involving a preview and a one-time token.
What you can do with it
- 1Automate recurring greetingsAsk your assistant to set up automated birthday or anniversary eCard workflows.
- 2Execute bulk messagingInstruct the AI to initiate a scheduled campaign to a group of recipients.
- 3Maintain recipient listsHave the assistant add or update team members within your eCardWidget directory.
- 4Create custom widgetsUse natural language to generate new widgets for your account.
Written from the project's README. Every use case is checked against a quote from it.
How to install eCardWidget MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall eCardWidget MCP in Claude Code
$ claude mcp add --env 'ECW_API_KEY=<YOUR_ECW_API_KEY>' ecardwidget-mcp -- npx -y ecardwidget-mcpInstall eCardWidget MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"ecardwidget-mcp": {
"command": "npx",
"args": [
"-y",
"ecardwidget-mcp"
],
"env": {
"ECW_API_KEY": "<YOUR_ECW_API_KEY>"
}
}
}
}Install eCardWidget MCP in VS Code
.vscode/mcp.json
{
"servers": {
"ecardwidget-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ecardwidget-mcp"
],
"env": {
"ECW_API_KEY": "<YOUR_ECW_API_KEY>"
}
}
}
}Install eCardWidget MCP in VS Code CLI
$ code --add-mcp '{"name":"ecardwidget-mcp","type":"stdio","command":"npx","args":["-y","ecardwidget-mcp"],"env":{"ECW_API_KEY":"<YOUR_ECW_API_KEY>"}}'Install eCardWidget MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"ecardwidget-mcp": {
"command": "npx",
"args": [
"-y",
"ecardwidget-mcp"
],
"env": {
"ECW_API_KEY": "<YOUR_ECW_API_KEY>"
}
}
}
}Install eCardWidget MCP in Codex
$ codex mcp add ecardwidget-mcp --env 'ECW_API_KEY=<YOUR_ECW_API_KEY>' -- npx -y ecardwidget-mcpInstall eCardWidget MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.ecardwidget-mcp] command = "npx" args = ["-y", "ecardwidget-mcp"] [mcp_servers.ecardwidget-mcp.env] ECW_API_KEY = "<YOUR_ECW_API_KEY>"
Install eCardWidget MCP in Gemini CLI
$ gemini mcp add -s user -e 'ECW_API_KEY=<YOUR_ECW_API_KEY>' ecardwidget-mcp npx -- -y ecardwidget-mcpInstall eCardWidget MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"ecardwidget-mcp": {
"command": "npx",
"args": [
"-y",
"ecardwidget-mcp"
],
"env": {
"ECW_API_KEY": "<YOUR_ECW_API_KEY>"
}
}
}
}eCardWidget MCP tools 1
Detected from the READMEeCards
Configuration
ECW_API_KEYRequiredSecretScoped eCardWidget API key (Settings → Developers → API Keys). Used as a Bearer token.
ECW_BASE_URLOverride the API base URL (default https://app.ecardwidget.com). For custom domains / testing.
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableecardwidget/ecardwidget-mcp is public and reachablegithub.com/ecardwidget/ecardwidget-mcp ↗Pass
- Package names this repository as its sourceecardwidget-mcp names ecardwidget/ecardwidget-mcp as sourcenpmjs.com/package/ecardwidget-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-07-09github.com/ecardwidget/ecardwidget-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from ecardwidget-mcpPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model1 tool description and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubeCardWidget 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
| Variable | Required | Default | Description |
|---|---|---|---|
ECW_API_KEY |
yes | — | Your scoped API key (used as a Bearer token). |
ECW_BASE_URL |
no | https://app.ecardwidget.com |
Override only for a custom domain / testing. |
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
eCardWidget MCP questions
How do I add eCardWidget MCP to Claude Code?
Run claude mcp add --env 'ECW_API_KEY=<YOUR_ECW_API_KEY>' ecardwidget-mcp -- npx -y ecardwidget-mcp in your terminal. Add --scope user to make it available in every project.
How do I add eCardWidget MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does eCardWidget MCP provide?
It exposes 1 tool, including eCards.
How do I secure my eCardWidget connection?
You use a scoped API key that you generate and control yourself, ensuring the assistant can only perform actions permitted by that key.
Are there safeguards for destructive actions like deleting or sending campaigns?
Yes, destructive tools require a two-step confirmation process involving a preview and a one-time token.