Prompteden MCP Server

@prompteden/mcp-server

Track your brand in AI answers from your own agent

MCP server that lets Claude, Codex, Cursor and other MCP clients read your PromptEden data: projects, monitors, captured answers, and analytics.

PromptEden checks how AI answers talk about your business. Answer engines come from the live provider catalog (list_providers); a monitor target uses one of those provider keys. Coding-agent providers are omitted. This MCP server gives your own agent that data, so you can ask about it in Claude, Codex, Cursor, or any other MCP client you already use.

Your agent can list projects and monitors, pull captured answers (get_results returns the API JSON and accepts a since date), set up a new project or monitor, and check your plan and usage. This server does not add citation or competitor fields of its own. Creating a monitor starts recurring metered runs and uses credits. Other tools do not use credits. If you have the PromptEden analytics snippet on your site, the agent can also read visits that came from AI engines, set up goals, and check that the snippet is working. Read tools are marked read-only, and every write tool is marked non-destructive.

The server runs locally over stdio on Node 20 or later. Create an account on the web, then pass an API key from Settings > API Keys as PROMPTEDEN_API_KEY. The server does not store your key. PROMPTEDEN_BASE_URL is optional and, when set, must be https://app.prompteden.com.

npx -y @prompteden/mcp-server

The published package is a single file, dist/index.mjs.

Example prompts

1. Using PromptEden, fetch each monitor's results from the last 7 days and summarize the captured answers, including any competitor or cited-source fields the result JSON actually contains.
2. Create a PromptEden project for mysite.com, then add a monitor that runs once a day. Call list_providers and target two engines from that catalog with a prompt asking which local bakeries they would recommend.
3. How many visits did my site get from AI engines last week, and which pages did they land on?

Install and configure

Create an account on the web, then set PROMPTEDEN_API_KEY to an API key from Settings > API Keys. The server reads that key from the environment and does not write it to disk. PROMPTEDEN_BASE_URL is optional. When it is set, the only allowed origin is https://app.prompteden.com. Any other origin is rejected.

Claude Desktop

Add this to the Claude Desktop MCP config (claude_desktop_config.json):

{
  "mcpServers": {
    "prompteden": {
      "command": "npx",
      "args": ["-y", "@prompteden/mcp-server"],
      "env": {
        "PROMPTEDEN_API_KEY": "YOUR_PROMPTEDEN_API_KEY"
      }
    }
  }
}

Cursor

Add the same mcpServers entry to Cursor's MCP config (.cursor/mcp.json or Cursor Settings > MCP):

{
  "mcpServers": {
    "prompteden": {
      "command": "npx",
      "args": ["-y", "@prompteden/mcp-server"],
      "env": {
        "PROMPTEDEN_API_KEY": "YOUR_PROMPTEDEN_API_KEY"
      }
    }
  }
}

Generic mcpServers JSON

{
  "mcpServers": {
    "prompteden": {
      "command": "npx",
      "args": ["-y", "@prompteden/mcp-server"],
      "env": {
        "PROMPTEDEN_API_KEY": "YOUR_PROMPTEDEN_API_KEY",
        "PROMPTEDEN_BASE_URL": "https://app.prompteden.com"
      }
    }
  }
}

PROMPTEDEN_BASE_URL can be omitted.

Environment variables

Tools

Names and descriptions below are generated from the server's tools/list response (node scripts/tools-table.mjs).

This build registers 20 tools. Analytics tools are included (11): analytics_get_property, analytics_get_verification, analytics_get_traffic, analytics_get_overview, analytics_list_goals, analytics_create_goal, analytics_archive_goal, analytics_add_property_host, analytics_create_property, analytics_rotate_key, analytics_verify_property.

Security

• The API key stays in the environment. This process does not persist it, and tool results are checked so the configured key is not echoed back.
• Do not commit an API key, put one in a shell history you share, or paste one into a client config that is checked in.
• Prefer a scoped key from Settings > API Keys over sharing an account password with an agent.
• analytics_get_traffic and analytics_get_overview use totals: null to mean "no basis to report". That is not zero traffic.
• The site key from create or rotate is shown once. Treat it like a secret and do not store it in chat logs you keep.

Development

npm ci
npm run typecheck
npm run build
npm run mcpb
npm test
node dist/index.mjs --help
node smoke.mjs
npm pack --dry-run

npm run build typechecks, then bundles the MCP SDK, API client, and tool registry into dist/index.mjs. npm run mcpb packs that file into build/prompteden-mcp-<version>.mcpb (manifest version 0.3). The npm tarball does not include the .mcpb file. CI uploads it as a workflow artifact.

License

MIT. Copyright (c) 2026 Yulan Ventures LLC.