MCP Fathom Analytics
Análisis de Fathom de MCP
Un servidor no oficial del Protocolo de Contexto de Modelo ( MCP ) para acceder a los datos de Fathom Analytics mediante un asistente de IA. Esta implementación utiliza el SDK no oficial @mackenly/fathom-api para interactuar con la API de Fathom Analytics. No está afiliado, respaldado ni soportado por Fathom Analytics. Publicado en npm como un script npx .
Características
El servidor MCP proporciona las siguientes herramientas de Fathom Analytics:
Información de la cuenta
get-account: recupera detalles sobre tu cuenta de Fathom Analytics
Gestión de sitios
list-sites: enumera todos tus sitios de Fathom Analytics
Eventos
list-events: enumera los eventos de un sitio específico
Analítica
get-aggregation: Genere informes analíticos agregados con opciones flexibles de filtrado y agrupación
Seguimiento de visitantes
get-current-visitors: Obtenga datos en tiempo real sobre los visitantes actuales del sitio
Related MCP server: @datafast/mcp-server
Uso
Si usa Claude Desktop, puede agregar el servidor MCP mediante la configuración JSON ( más información ). Aquí tiene un ejemplo:
{
"mcpServers": {
"fathom-analytics": {
"command": "npx",
"args": [
"-y",
"mcp-fathom-analytics"
],
"env": {
"FATHOM_API_KEY": "your_api_key_here"
}
}
}
}Puede encontrar más información sobre otros clientes MCP aquí: Modelo Contexto Protocolo Clientes de ejemplo
Estructura de la API
El servidor MCP utiliza el SDK @mackenly/fathom-api para interactuar con los puntos finales de la API de Fathom Analytics:
API de cuenta :
https://api.usefathom.com/v1/accountAPI de sitios :
https://api.usefathom.com/v1/sitesAPI de eventos :
https://api.usefathom.com/v1/sites/SITE_ID/eventsAPI de agregación :
https://api.usefathom.com/v1/aggregationsAPI de visitantes actuales :
https://api.usefathom.com/v1/current_visitors
Ejemplos de agregación
La herramienta de agregación es muy flexible. A continuación, se muestran algunos ejemplos de uso:
Estadísticas diarias de visitas a la página de los últimos 30 días :
{
"entity": "pageview",
"entity_id": "SITE_ID",
"aggregates": "pageviews,uniques,visits",
"date_grouping": "day",
"date_from": "2023-08-01 00:00:00"
}Rendimiento de páginas individuales :
{
"entity": "pageview",
"entity_id": "SITE_ID",
"aggregates": "pageviews,uniques,avg_duration",
"field_grouping": "pathname",
"sort_by": "pageviews:desc",
"limit": 10
}Tráfico de países específicos :
{
"entity": "pageview",
"entity_id": "SITE_ID",
"aggregates": "visits",
"field_grouping": "country_code",
"sort_by": "visits:desc"
}Contribuyendo
¡Agradecemos sus contribuciones! No dude en enviar una solicitud de incorporación de cambios.
Licencia
Este proyecto está licenciado bajo la licencia MIT: consulte el archivo de LICENCIA para obtener más detalles.
Available Tools
5 toolsget-accountB
Get Fathom Analytics account information
Inputs: no named parameters.
get-aggregationC
Get aggregated analytics data from Fathom
Inputs: entity (required), entity_id (required), aggregates (required), date_from (required), +7 more.
get-current-visitorsC
Get current visitors for a Fathom Analytics site
Inputs: site_id (required), detailed.
list-eventsB
List all events for a Fathom Analytics site (automatically handles pagination)
Inputs: site_id (required), limit.
list-sitesC
List all Fathom Analytics sites on the account
Inputs: limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose targeting different resources: account info, aggregated data, current visitors, events, and sites. There is no overlap in functionality, making it easy for an agent to select the right tool without confusion.
All tool names follow a consistent verb_noun pattern using hyphen-separated lowercase words (e.g., get-account, list-sites). The naming is predictable and uniform across all tools, enhancing readability and usability.
With 5 tools, the server is well-scoped for analytics purposes, covering key operations like retrieving account details, aggregated data, real-time visitors, events, and sites. Each tool earns its place without being overly sparse or bloated.
The tool set provides comprehensive read-only coverage for analytics data, including account, sites, events, and current visitors. A minor gap exists in write operations (e.g., creating or updating sites/events), but agents can still perform most common analytics tasks effectively.
Maintenance
Related MCP Connectors
Privacy-first, cookie-free web analytics. Read stats and manage sites from your AI.
AI access to Hitsteps analytics, live visitors, uptime, goals, alerts, and chats.
Ask an assistant about your website traffic. Privacy-first web analytics, no cookies. OAuth.
Privacy-first web analytics. Query pageviews, referrers, trends, and AI insights.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to query privacy-first web analytics from Measure.events, including pageviews, top pages, referrers, and custom event tracking, all via natural language.62MIT
- AlicenseAqualityDmaintenanceExposes DataFast analytics as tools for AI assistants, enabling natural language queries about website metrics such as visitors, referrers, revenue, and real-time data.221MIT
- FlicenseNot gradedqualityDmaintenanceConnects AI assistants to the Fathom meeting recording API to retrieve meeting summaries, transcripts, and action items.-
- AlicenseAqualityFmaintenanceUnofficial MCP server that lets AI agents query Aptabase analytics using cookie-authenticated dashboard endpoints, providing tools for metrics, events, and sessions.171MIT