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 PROMPTEDENAPIKEY. The server does not store your key. PROMPTEDENBASEURL 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 PROMPTEDENAPIKEY to an API key from Settings > API Keys. The server reads that key from the environment and does not write it to disk. PROMPTEDENBASEURL 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 (claudedesktopconfig.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"
      }
    }
  }
}

PROMPTEDENBASEURL can be omitted.

Environment variables

Tools

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

Shortened. The full README is on GitHub.