Business operationsPublic source

Analytics MCP Server

Governed analytics platform for AI agents — metrics, dashboards, funnels, cohorts, anomaly detection, forecasting, and policy enforcement. 28 tools with full audit trail.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides analytics capabilities through a typed MCP contract.

Architecture

How Analytics MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Analytics MCP Server

Validates the request and owns 28 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Analytics MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Analytics MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

28 named tools

list_data_sources

List all connected data sources

read only

list_datasets

List all available datasets/tables

read only

describe_dataset

Describe a dataset — schema, row count, freshness

read only

list_metrics

List all defined metrics

read only

get_metric_definition

Get full metric definition

read only

query_metric

Query a metric over a time range

read only

breakdown_metric

Break down a metric by dimension

read only

compare_metric

Compare a metric across two periods

read only

query_events

Query raw events with filters

read only

query_report

Run a saved/named report

read only

analyze_funnel

Analyze funnel conversion rates

read only

analyze_cohort

Analyze cohort retention

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

22 read only3 internal write3 governance

Pre-query validation — validate_analytics_policy checks before data access
Export risk assessment — check_export_risk flags PII and large exports
Approval workflow — request_data_access for restricted resources
Full audit trail — every query logged with timestamp, params, result
No raw SQL — prevents injection and uncontrolled data access

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

Resources

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-analytics

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-analytics",
    ["mcp-analytics"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring