Ecardwidget MCP

Name: Ecardwidget MCP
Author: eCardWidget

by eCardWidgetversion 0.5.2i★ –iRuns on your computer

Registry nameio.github.eCardWidget/ecardwidget-mcp

Install

Overview

Description from the maker (original English)

Send eCards, run bulk campaigns, and automate recurring cards from your AI assistant.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: ECW_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: ECW_API_KEY, ECW_BASE_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add ecardwidget --env ECW_API_KEY=your-value --env ECW_BASE_URL=your-value -- npx -y ecardwidget-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ecardwidget": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ecardwidget-mcp"
      ],
      "env": {
        "ECW_API_KEY": "your-value",
        "ECW_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

ECW_API_KEY secret required env
Scoped eCardWidget API key (Settings → Developers → API Keys). Used as a Bearer token.
ECW_BASE_URL env
Override the API base URL (default https://app.ecardwidget.com). For custom domains / testing.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account eCardWidget, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32464 servers in this category
Published to the registry more recently than 16% of the other 32464 servers in this category
Basic checks equal to or better than 100% of the other 32464 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Ecardwidget MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: ECW_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.2) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, yontu

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

yontu

by senrecep

Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

eCardWidget MCP Server

The official Model Context Protocol server for [eCardWidget](https://www.ecardwidget.com). 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

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

yontu

README from the maker

eCardWidget MCP Server

Quick start

Option A — Claude Desktop (one click)

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

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

Configuration

Tools

Guided flows (prompts)

Security

Development

License