Microsoft Clarity API + MCP Server + A2A Server
Project description
Microsoft Clarity API
Version: 2.0.1
Microsoft Clarity API + MCP Server + A2A Agent
clarity-api is a typed, action-routed connector for the
Microsoft Clarity Data Export API,
built on agent-utilities. It
ships a Python Api client, a FastMCP MCP server
(clarity-mcp), and an optional Pydantic-AI A2A agent server (clarity-agent).
It works with the dashboard data — structured over a specified date range and broken down by up to three dimensions.
This repository is actively maintained — contributions are welcome!
Table of Contents
- Architecture
- Key Features
- Available MCP Tools
- Dynamic Tool Selection
- Environment Variables
- Configuration
- Agent
- Usage (Python client)
- Security & Governance
- Installation
- Documentation
- Contributing
Architecture
clarity-api follows the standard agent-package layering: a typed REST client at
the bottom, an action-routed MCP tool layer in the middle, and an optional
Pydantic-AI A2A agent server on top. The MCP tool depends on an injected client
via Depends(get_client), which resolves credentials (OIDC delegation or a fixed
CLARITY_TOKEN) before talking to the Microsoft Clarity REST API.
graph TD
User(["User / A2A Client"]) --> Agent["clarity-agent<br/>Pydantic-AI A2A Server"]
Agent --> MCP["clarity-mcp<br/>FastMCP Server"]
MCP --> Tool["clarity_insights tool<br/>(CONCEPT:CLA-001)"]
Tool -->|Depends get_client| Auth["get_client<br/>auth.py"]
Tool --> Service["InsightsService<br/>clarity_api/services/"]
Auth --> Client["Api facade<br/>clarity_api/api/"]
Service --> Client
Client --> Clarity(["Microsoft Clarity<br/>Data Export REST API"])
| Layer | Module | Responsibility |
|---|---|---|
| Agent | clarity_api/agent_server.py |
Pydantic-AI A2A server, AG-UI web interface |
| Tooling | clarity_api/mcp/, clarity_api/mcp_server.py |
Action-routed MCP tool registration |
| Service | clarity_api/services/ |
InsightsService — dependency-injected data-export use case |
| Auth seam | clarity_api/auth.py |
get_client dependency: OIDC delegation / fixed token |
| Client | clarity_api/api/ |
ClarityApiBase + ClarityApiInsights mixins composed into Api |
| Models | clarity_api/clarity_models.py |
Pydantic request/response validation |
Key Features
- Typed Python client —
clarity_api.api_client.Api, composed from modular per-domain mixins inclarity_api/api/, validating credentials againstGET /projects. - Action-routed MCP tool —
clarity_insights(CONCEPT:CLA-001) consolidates the Data Export surface to minimize LLM token overhead. - A2A agent server —
clarity-agentauto-discovers the MCP tools and exposes an AG-UI web interface. - Enterprise-ready — inherits OIDC auth, OpenTelemetry, audit logging, prompt-injection
defense, and guardrails from
agent-utilities.
Available MCP Tools
Auto-generated — do not edit (synced by the mcp-readme-table pre-commit hook).
Condensed action-routed tools (default — MCP_TOOL_MODE=condensed)
| MCP Tool | Toggle Env Var | Description |
|---|---|---|
clarity_insights |
INSIGHTSTOOL |
Retrieve Microsoft Clarity dashboard data insights for a project. |
Verbose 1:1 API-mapped tools (MCP_TOOL_MODE=verbose or both)
1 per-operation tools — one per public API method (click to expand)
| MCP Tool | Toggle Env Var | Description |
|---|---|---|
clarity_get_data_export |
CLARITY_API_INSIGHTSTOOL |
Retrieve dashboard data insights for a project. |
1 action-routed tool(s) (default) · 1 verbose 1:1 tool(s). Each is enabled unless its <DOMAIN>TOOL toggle is set false; MCP_TOOL_MODE selects the surface (condensed default · verbose 1:1 · both). Auto-generated — do not edit.
Parameters
number_of_days(1, 2, or 3): last 24, 48, or 72 hours.dimension_1,dimension_2,dimension_3: breakdown dimensions.
Dimension Options
Browser, Device, Country, OS, Source, Medium, Campaign, Channel, URL.
Dynamic Tool Selection
Each tool domain is gated behind an env toggle so deployments can trim their surface:
| Toggle | Default | Domain |
|---|---|---|
INSIGHTSTOOL |
True |
clarity_insights |
Environment Variables
Package environment variables
| Variable | Example | Description |
|---|---|---|
HOST |
0.0.0.0 |
|
PORT |
8000 |
|
TRANSPORT |
stdio |
options: stdio, streamable-http, sse |
FASTMCP_LOG_LEVEL |
ERROR |
FastMCP log verbosity |
NO_COLOR |
1 |
|
TERM |
dumb |
|
ENABLE_OTEL |
True |
|
OTEL_EXPORTER_OTLP_ENDPOINT |
http://localhost:8080/api/public/otel |
|
OTEL_EXPORTER_OTLP_PUBLIC_KEY |
pk-... |
|
OTEL_EXPORTER_OTLP_SECRET_KEY |
sk-... |
|
OTEL_EXPORTER_OTLP_PROTOCOL |
http/protobuf |
|
EUNOMIA_TYPE |
none |
options: none, embedded, remote |
EUNOMIA_POLICY_FILE |
mcp_policies.json |
|
EUNOMIA_REMOTE_URL |
http://eunomia-server:8000 |
|
CLARITY_URL |
https://www.clarity.ms |
|
CLARITY_TOKEN |
your_clarity_token_here |
|
CLARITY_SSL_VERIFY |
True |
|
INSIGHTSTOOL |
True |
Inherited agent-utilities variables (apply to every connector)
| Variable | Example | Description |
|---|---|---|
MCP_TOOL_MODE |
condensed |
Tool surface: condensed |
MCP_ENABLED_TOOLS |
— | Comma-separated tool allow-list |
MCP_DISABLED_TOOLS |
— | Comma-separated tool deny-list |
MCP_ENABLED_TAGS |
— | Comma-separated tag allow-list |
MCP_DISABLED_TAGS |
— | Comma-separated tag deny-list |
MCP_CLIENT_AUTH |
— | Outbound MCP auth (oidc-client-credentials for fleet calls) |
OIDC_CLIENT_ID |
— | OIDC client id (service-account auth) |
OIDC_CLIENT_SECRET |
— | OIDC client secret (service-account auth) |
DEBUG |
False |
Verbose logging |
PYTHONUNBUFFERED |
1 |
Unbuffered stdout (recommended in containers) |
MCP_URL |
http://localhost:8000/mcp |
URL of the MCP server the agent connects to |
PROVIDER |
openai |
LLM provider for the agent |
MODEL_ID |
gpt-4o |
Model id for the agent |
ENABLE_WEB_UI |
True |
Serve the AG-UI web interface |
18 package + 14 inherited variable(s). Auto-generated from .env.example + the shared agent-utilities set — do not edit.
All runtime configuration is supplied via environment variables (or a .env
file — see .env.example). Never commit real tokens.
Clarity credentials
| Variable | Default | Description |
|---|---|---|
CLARITY_URL |
https://www.clarity.ms |
Base URL of the Microsoft Clarity instance. |
CLARITY_TOKEN |
(none) | Bearer API token generated in the Clarity project settings. Required unless OIDC delegation is enabled. |
CLARITY_SSL_VERIFY |
True |
Whether to verify TLS certificates when calling the Clarity API. |
MCP server / transport
| Variable | Default | Description |
|---|---|---|
TRANSPORT |
stdio |
MCP transport: stdio, streamable-http, or sse. |
HOST |
0.0.0.0 |
Bind host for HTTP transports. |
PORT |
8000 |
Bind port for HTTP transports. |
AUTH_TYPE |
none |
MCP server auth scheme inherited from agent-utilities (e.g. none, oidc). |
FASTMCP_LOG_LEVEL |
ERROR |
FastMCP log verbosity. Set to ERROR at startup to suppress log spam. |
INSIGHTSTOOL |
True |
Toggle registration of the clarity_insights tool (see Dynamic Tool Selection). |
Telemetry & access governance
| Variable | Default | Description |
|---|---|---|
ENABLE_OTEL |
True |
Enable OpenTelemetry export of traces/metrics. |
EUNOMIA_TYPE |
none |
Eunomia authorization mode: none, embedded, or remote. |
EUNOMIA_POLICY_FILE |
mcp_policies.json |
Path to the local Eunomia policy file (embedded mode). |
Build / terminal (set automatically — usually no action needed)
| Variable | Default | Description |
|---|---|---|
UV_COMPILE_BYTECODE |
1 |
Set in the Docker image to precompile bytecode for faster cold starts. |
NO_COLOR / TERM |
1 / dumb |
Terminal-control variables set at MCP startup to keep stdio transport output machine-clean. Not app configuration — listed for completeness. |
Configuration
Install the slim
[mcp]extra. The examples below installclarity-api[mcp]— the MCP-server extra that pulls only the FastMCP / FastAPI tooling (agent-utilities[mcp]). It deliberately excludes the heavy agent runtime (the epistemic-graph engine,pydantic-ai,dspy,llama-index,tree-sitter), souvx/container installs are dramatically smaller and faster. Use the full[agent]extra only when you need the integrated Pydantic AI agent (see Installation).
stdio (local agent integration)
{
"mcpServers": {
"clarity-api": {
"command": "uv",
"args": ["run", "--with", "clarity-api[mcp]", "clarity-mcp"],
"env": {
"CLARITY_URL": "https://www.clarity.ms",
"CLARITY_TOKEN": "<YOUR_CLARITY_TOKEN>"
}
}
}
}
Streamable HTTP
export CLARITY_URL=https://www.clarity.ms
export CLARITY_TOKEN=<your-clarity-token>
clarity-mcp --transport streamable-http --host 0.0.0.0 --port 8000
Docker
docker pull knucklessg1/clarity-api:mcp
docker compose -f docker/mcp.compose.yml up -d
The
:mcptag is the slim MCP-server image (built fromdocker/Dockerfile --target mcp, installingclarity-api[mcp]). The default:latesttag is the full agent image (--target agent,clarity-api[agent]) which also bundles the Pydantic AI agent and the epistemic-graph engine — use it when you runclarity-agent(the agent), not just the MCP server. See Container images.
Additional Deployment Options
clarity-api can also run as a local container (Docker / Podman / uv) or be
consumed from a remote deployment. The
Deployment guide has full, copy-paste
mcp_config.json for all four transports — stdio, streamable-http,
local container / uv, and remote URL:
- Local container / uv — launch the server from
mcp_config.jsonviauvx,docker run, orpodman run, or point at a local streamable-http container byurl. - Remote URL — connect to a server deployed behind Caddy at
http://clarity-mcp.arpa/mcpusing the"url"key.
Agent
The clarity-agent entry point (clarity_api/agent_server.py) starts a
Pydantic-AI A2A server that auto-discovers the MCP tools and exposes an AG-UI web
interface.
Run locally
clarity-agent --web --provider openai --model-id gpt-4o
The agent reads its identity from clarity_api/agent_data/IDENTITY.md and discovers
tools via mcp_config.json.
Deploy with Docker Compose
docker/agent.compose.yml runs the MCP server and the agent server side by side;
the agent connects to the MCP server over MCP_URL:
services:
clarity-api-mcp:
image: knucklessg1/clarity-api:mcp
restart: always
env_file: [ ../.env ]
environment:
- HOST=0.0.0.0
- PORT=8000
- TRANSPORT=streamable-http
ports: [ "8000:8000" ]
clarity-api-agent:
image: knucklessg1/clarity-api:latest
restart: always
depends_on: [ clarity-api-mcp ]
command: [ "clarity-agent" ]
env_file: [ ../.env ]
environment:
- HOST=0.0.0.0
- PORT=9017
- MCP_URL=http://clarity-api-mcp:8000/mcp
- PROVIDER=${PROVIDER:-openai}
- MODEL_ID=${MODEL_ID:-gpt-4o}
- ENABLE_WEB_UI=True
- ENABLE_OTEL=True
ports: [ "9017:9017" ]
docker compose -f docker/agent.compose.yml up -d
Usage (Python client)
#!/usr/bin/python
# coding: utf-8
import clarity_api
token = "<TOKEN>"
url = "https://www.clarity.ms"
client = clarity_api.Api(url=url, token=token)
response = client.get_data_export(number_of_days=2, dimension_1="OS", dimension_2="Channel")
print("Status Code:", response.status_code)
print("JSON Output:", response.json())
Security & Governance
clarity-api inherits enterprise infrastructure from agent-utilities: JWT/OIDC
authentication, OpenTelemetry instrumentation, HashiCorp Vault secret resolution,
append-only audit logging (agent-utilities OS-5.4), prompt-injection defense
(OS-5.1), and the guardrail engine (OS-5.3). The connector stays
inactive until CLARITY_URL and CLARITY_TOKEN are configured. Never commit .env
files or tokens.
Installation
Pick the extra that matches what you want to run:
| Extra | Installs | Use when |
|---|---|---|
| (none) | the bare Api Python client (requests) |
You only use the clarity_api.Api client |
clarity-api[mcp] |
Slim MCP server (agent-utilities[mcp] — FastMCP/FastAPI) |
You only run the MCP server (smallest install / image) |
clarity-api[agent] |
Full agent runtime (agent-utilities[agent,logfire] — Pydantic AI + the epistemic-graph engine) |
You run the integrated agent |
clarity-api[all] |
Everything (mcp + agent) |
Development / both surfaces |
# MCP server only (recommended for tool hosting — slim deps)
uv pip install "clarity-api[mcp]"
# Full agent runtime (Pydantic AI + epistemic-graph engine)
uv pip install "clarity-api[agent]"
# Everything (development)
uv pip install "clarity-api[all]" # or: python -m pip install "clarity-api[all]"
Container images (:mcp vs :agent)
One multi-stage docker/Dockerfile builds two right-sized images, selected by --target:
| Image tag | Build target | Contents | Entrypoint |
|---|---|---|---|
knucklessg1/clarity-api:mcp |
--target mcp |
clarity-api[mcp] — slim, no engine/pydantic-ai/dspy/llama-index/tree-sitter |
clarity-mcp |
knucklessg1/clarity-api:latest |
--target agent (default) |
clarity-api[agent] — full agent runtime + epistemic-graph engine |
clarity-agent |
docker build --target mcp -t knucklessg1/clarity-api:mcp docker/ # slim MCP server
docker build --target agent -t knucklessg1/clarity-api:latest docker/ # full agent
docker/mcp.compose.yml runs the slim :mcp server; docker/agent.compose.yml runs the
agent (:latest) with a co-located :mcp sidecar.
Knowledge-graph database (epistemic-graph)
The full agent ([agent] / :latest) embeds the epistemic-graph engine (pulled in
transitively via agent-utilities[agent]). For production — or to share one knowledge graph
across multiple agents — run epistemic-graph as its own database container and point the
agent at it instead of embedding it. Deployment recipes (single-node + Raft HA), connection
config, and the full database architecture (with diagrams) are documented in the
epistemic-graph deployment guide.
The slim [mcp] server does not require the database.
Obtaining Access Tokens
Note: Only project admins can manage access tokens.
- Go to your Clarity project. Select
Settings→Data Export→Generate new API token. - Provide a descriptive name for the token for easy identification.
Documentation
Contributing
Contributions are welcome. Run quality checks before pushing:
pre-commit run --all-files
python -m pytest -q
Deploy with agent-os-genesis
This package can be provisioned for you — skill-guided — by the agent-os-genesis
universal skill (its single-package deploy mode): it picks your install method, seeds
secrets to OpenBao/Vault (or .env), trusts your enterprise CA, registers the MCP
server, and verifies it — the same machinery that stands up the whole Agent OS, narrowed
to just this package. Ask your agent to "deploy clarity-api with agent-os-genesis".
| Install mode | Command |
|---|---|
| Bare-metal, prod (PyPI) | uvx clarity-mcp · or uv tool install clarity-api |
| Bare-metal, dev (editable) | uv pip install -e ".[all]" · or pip install -e ".[all]" |
| Container, prod | deploy knucklessg1/clarity-api:latest via docker-compose / swarm / podman / podman-compose / kubernetes |
| Container, dev (editable) | deploy docker/compose.dev.yml (source-mounted at /src; edits live on restart) |
Secrets are read-existing + seeded via vault_sync — you are only prompted for what's missing.
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file clarity_api-2.0.1.tar.gz.
File metadata
- Download URL: clarity_api-2.0.1.tar.gz
- Upload date:
- Size: 39.8 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.14.4
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
917d51aa7d6b8b7eed63b98cfffc1bd91c4939704ab19bd913730c4cdff13242
|
|
| MD5 |
916598e5b438e5eb07ce92e958eb12b1
|
|
| BLAKE2b-256 |
c9426dcff60e0ecc98a8ec7ce757059114d2f0019327294b92da75a115bc9dd2
|
File details
Details for the file clarity_api-2.0.1-py3-none-any.whl.
File metadata
- Download URL: clarity_api-2.0.1-py3-none-any.whl
- Upload date:
- Size: 44.4 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.14.4
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
00757b1901bcfa3efc4799e88cfdb7199f29dbf7af955b3a628ce929f7074d0a
|
|
| MD5 |
9a899f84548d687ab4eeba9784cd4d5d
|
|
| BLAKE2b-256 |
4c06dc7f2fff4a93752f83202ad9784fed554c1ad3b453b307f6fd6c114dac13
|