PostHog MCP Server
Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
Description from the maker (original English)
Send eCards, run bulk campaigns, and automate recurring cards from your AI assistant.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ECW_API_KEY, ECW_BASE_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
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-mcpFill in the empty values before running it.
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.
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.
ECW_BASE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 10, 2026
The registry name was verified with the GitHub account eCardWidget, which owns the repo
Code last changed 4 months ago
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 2 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.
You need to fill in: ECW_API_KEY
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).
The GitHub repo last changed 4 months ago, and the latest version (0.5.2) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: PostHog MCP Server, Agent-Native Analytics, Openshorts
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
Agent-Native Amplitude/Mixpanel - connect data sources, prompt for charts
Turn long videos into viral vertical shorts and publish them to TikTok, Instagram and YouTube.
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.
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.
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:
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.
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.)
{
"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.
| 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. |
All tools are namespaced ecw_*; only those your key is scoped for are registered.
ecw_whoami, ecw_describe_fields (what fields you can set on a widget / eCard / campaign / automation — synced from the OpenAPI spec)ecw_search_ecards, ecw_get_widget_ecards, ecw_create_ecard (image via URL or base64), ecw_send_ecard, ecw_delete_ecardecw_list_team_members, ecw_find_team_member, ecw_upsert_team_member, ecw_import_team_members, ecw_deactivate_team_member, ecw_delete_team_memberecw_list_widgets, ecw_create_widget, ecw_duplicate_widget, ecw_delete_widgetecw_list_automations, ecw_create_automation (birthday / anniversary / onboarding)ecw_list_campaigns, ecw_create_campaign (draft), ecw_send_campaignDestructive 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.
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"*.
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.
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)
MIT