Get started

Overview

Connect AI assistants to Egaki campaign analytics.

Egaki Analytics MCP is a hosted server that connects MCP-compatible AI assistants to the analytics already available in your Egaki dashboard. Instead of looking up campaign IDs and metrics manually, you can ask an assistant to find an authorized campaign and analyze it with you.

MCP endpointhttps://mcp.egaki.ai/api/mcp

What is Egaki MCP?

Egaki MCP implements the Model Context Protocol, an open standard for connecting AI applications to external systems. An MCP client connects to Egaki, authenticates the user with OAuth, then calls read-only analytics tools on that user’s behalf.

Why use Egaki MCP?

It makes the campaign data you already rely on available in the AI tool where you are planning, researching, or reporting. You can start broad—“Which of my campaigns needs attention?”—then drill into visibility, citations, sentiment, prompts, competitors, and traffic without leaving the conversation.

Start with a natural question

“List my accessible Egaki campaigns, then show the latest overview for the campaign with the weakest share of voice.”

What can you do?

Egaki MCP currently exposes these read-only analytics capabilities.

list_campaignsFind campaigns available to you.

get_campaign_overviewReview current health metrics and priority actions.

get_llm_visibilityAnalyze rank and share of voice by platform and persona.

get_citationsInspect citation rates, domains, and source URLs.

get_sentimentTrack positive, neutral, and negative sentiment trends.

get_competitorsIdentify competitor presence and outranking signals.

get_prompt_trackingMeasure brand mentions by prompt group.

get_visibility_attributionSee owned pages contributing to visibility.

get_pipelineExplore demand, opportunity, and missed prompts.

get_traffic_analysisReview visits, sources, sessions, and landing pages.

Campaign access

Egaki MCP only lists and analyzes campaigns that the signed-in user can already access in Egaki. It enforces organization membership, special campaign allowlists, campaign-level database policies, and terminated-access restrictions on every request.

Your assistant never receives unrestricted account access. Every response is scoped to the user who completed OAuth, and the MCP does not expose write actions.

Connect with Claude

In Claude, open Customize → Connectors.
Select Add custom connector and enter the MCP endpoint.
Complete the Egaki OAuth sign-in and consent flow.
Enable the Egaki connector in a conversation and ask a campaign question.

Your Egaki administrator manages the connector’s OAuth client configuration.

Authentication

Egaki MCP uses OAuth. You sign in with your existing Egaki account, and the authorization server issues a token specifically bound to the Egaki MCP endpoint. Standard dashboard session tokens cannot be used to access the MCP.

Never paste an access token or OAuth client secret into an AI chat.

Need help?

If a campaign is missing, ask your Egaki administrator to confirm your organization membership and campaign access. If a connector cannot sign in, disconnect it, reconnect it, and complete OAuth again.