For coding agents

Discover EventDash, install the tracker, and query analytics over MCP. Do not invent keys.

Tracking keys vs MCP tokens

ed_ keys go in the public snippet only. edt_ and edr_ are for MCP. Never paste secrets into chat.

Agent files

Plain text the model can fetch in one hop

/llms.txt — product facts, comparisons, guides, and install index for answer engines

/.well-known/api-catalog — RFC 9727 API catalog with OpenAPI links

/.well-known/mcp/server-card.json — MCP Server Card (Streamable HTTP endpoint and capabilities)

/.well-known/agent-skills/index.json — Agent Skills discovery index

/.well-known/ai-catalog.json — ARD capability manifest (MCP, OpenAPI, skill)

/ai.txt — crawl/citation policy for AI systems

/llms-full.txt — full install and MCP docs

/AGENTS.md — instructions for the user's repo

Markdown for agents: send Accept: text/markdown on any public HTML page. HTML stays the default for browsers. Docs also have .md twins, e.g. /docs/quickstart.md

Install the skill

Teaches the agent to add the tracker and data-ed-goal

Save the skill into the project (Cursor reads .cursor/skills; Claude Code reads .claude/skills).

bash

mkdir -p .cursor/skills/eventdash
curl -fsSL https://www.eventda.sh/skills/eventdash/SKILL.md -o .cursor/skills/eventdash/SKILL.md
curl -fsSL https://www.eventda.sh/skills/eventdash/reference.md -o .cursor/skills/eventdash/reference.md

Source: https://www.eventda.sh/skills/eventdash/SKILL.md

Query analytics

MCP is read-only. Connect from MCP docs. Browser agents can also use WebMCP tools on this site for public docs search and navigation. They cannot create accounts or API keys.

Quick start Connect MCP