# ecardwidget-mcp [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/eCardWidget/ecardwidget-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 210  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ecardwidget-mcp

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

## Tools
Capabilities this server exposes over MCP:

- **ecw_whoami**
- **ecw_describe_fields**
- **ecw_search_ecards**
- **ecw_get_widget_ecards**
- **ecw_create_ecard**
- **ecw_list_team_members**
- **ecw_find_team_member**
- **ecw_upsert_team_member**
- **ecw_list_widgets**
- **ecw_create_widget**
- **ecw_duplicate_widget**
- **ecw_delete_widget**
- **ecw_list_automations**
- **ecw_create_automation**
- **ecw_list_campaigns**
- **ecw_create_campaign**
- **ecw_send_campaign**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "ecardwidget-mcp": {
    "command": "npx",
    "args": ["-y","ecardwidget-mcp"]
  }
}
```

## Documentation & README

# eCardWidget MCP Server

[![npm](https://img.shields.io/npm/v/ecardwidget-mcp.svg)](https://www.npmjs.com/package/ecardwidget-mcp)

The official [Model Context Protocol](https://modelcontextprotocol.io) 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](https://github.com/eCardWidget/ecardwidget-mcp/releases)
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)

```bash
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)

```json
{
  "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](https://github.com/eCardWidget/ecardwidget-mcp/blob/HEAD/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

```bash
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