Skip to content

Claude Code

Claude Code

Use the plugin path first. It gives Claude Code both the MCP server connection and the analytics-specific workflow layer in one install.

  • An Agent Analytics account at app.agentanalytics.sh
  • Claude Code installed locally
  • Access to the same GitHub or Google identity you use for Agent Analytics
Terminal window
/plugin marketplace add Agent-Analytics/agent-analytics-plugin
/plugin install agent-analytics

This is the shortest hosted path for Claude Code because it packages the MCP connection and the usage guidance together.

Ask Claude Code:

  • List my Agent Analytics projects
  • How is my-site doing this week?
  • What are the top pages for my-site this week?

If the plugin is working, Claude Code should be able to reach your account without asking you to hand-roll HTTP requests.

If you have not created your first real project yet, go back to Getting Started and do that next.

If you do not want the full plugin, use the skill path before raw MCP:

Terminal window
npx skills add Agent-Analytics/agent-analytics-mcp

This path teaches Claude Code how to set up tracking, query analytics, and run experiments. It still requires a valid Agent Analytics API key in the environment used by Claude Code.

Lower-level fallback: add only the MCP server

Section titled “Lower-level fallback: add only the MCP server”

If you want the MCP server without the plugin or skill layer:

Terminal window
claude mcp add agent-analytics --transport http https://mcp.agentanalytics.sh/mcp

Use --transport http. The hosted MCP server is not configured for legacy SSE transport.

  • Make sure Claude Code is using the same GitHub or Google account as your Agent Analytics dashboard account.
  • If the skill installs but Claude Code cannot query data, confirm the environment exposes AGENT_ANALYTICS_API_KEY.
  • If the MCP command fails, verify you used --transport http.