MCP Fathom Analytics
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FATHOM_API_KEY | Yes | Your Fathom Analytics API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-accountB | Get Fathom Analytics account information |
| list-sitesC | List all Fathom Analytics sites on the account |
| list-eventsB | List all events for a Fathom Analytics site (automatically handles pagination) |
| get-aggregationC | Get aggregated analytics data from Fathom |
| get-current-visitorsC | Get current visitors for a Fathom Analytics site |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.