PromptEden

What PromptEden MCP server does

The PromptEden MCP server gives an agent access to PromptEden account data, projects, monitors, captured monitor results, answer-engine provider metadata, and agent-key status. It can create projects and monitors as well as retrieve existing records. Monitor creation requires a project reference and a provider key returned by list_providers; creating a monitor starts recurring metered runs.

Analytics tools expose property configuration, collector state, verification results, AI-referral traffic, overview metrics, goals, and landing-page or engine breakdowns. Content-agent tools read fleet configuration and recent output, then submit proposed configure, activate, pause, resume, approve, or veto actions for human approval. Stored content-agent text is treated as untrusted data.

How it works

The PromptEden MCP server is a local Node.js process that communicates with an MCP client over stdio. The client starts the published package with npx, and the process sends authenticated requests to the PromptEden API. Read operations return API data; they do not independently add citation or competitor fields to monitor results.

Analytics responses distinguish unavailable data from zero values. For example, a null traffic total means the collector cannot support a report, not that traffic was zero. Goal reporting uses within-visit attribution, counts at most one completion per goal per visit, and starts counting prospectively after goal creation.

Setup and configuration

Create a PromptEden account and obtain an API key from Settings > API Keys. Set PROMPTEDEN_API_KEY in the MCP client's environment, then run:

npx -y @prompteden/mcp-server

PROMPTEDEN_BASE_URL is optional and defaults to https://app.prompteden.com. If supplied, it must use that exact origin. The server reads the API key from the environment and does not write it to disk. The documented client configurations include Claude Desktop and Cursor; the same mcpServers structure can be used with other MCP clients.

Tools and capabilities

Core tools can retrieve account plan and usage, list or inspect projects, list monitors, fetch results, enumerate available answer engines, and check API-agent status. get_results accepts a since date, allowing an agent to request recent captured results.

Analytics tools can create an analytics property, rotate its ingest key, add a collection hostname, start or inspect verification, read traffic and overview reports, and create, list, or archive destination-URL goals. A newly created site key is displayed once, so it should be installed immediately. Archiving a goal preserves its history.

Content-agent operations are approval-oriented rather than direct uncontrolled writes. Configuration and publication decisions are restricted by team settings, plan limits, publication-session ownership, and review handles returned by the output-review tool.

Limitations and notes

The PromptEden MCP server requires a valid API key and access scopes; agent_status requires account:read. Coding-agent providers are excluded from the provider catalog, and monitor targets must use keys from that filtered catalog. Creating a monitor consumes credits; the supplied descriptions identify the other tools as non-credit-consuming.

Analytics property creation, key rotation, host changes, goal creation, and goal archival affect live tracking or collection behavior. Verification is asynchronous: start it with the verification tool and poll for its actual status rather than inferring success. Analytics keys cannot be re-read after creation; rotation issues a replacement key. A project with multiple properties may require an unambiguous property reference.