Fathom Analytics MCP integration for AI agents.
Connect AI agents to Fathom Analytics through 15 structured actions, including get account, create event, and create milestone. Review authentication, inputs…
- ACTION CONTRACTS
- 15
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Fathom Analytics integration exposes
The Fathom Analytics Agent App exposes 15 provider-backed actions for data work. Its current contract lets an authorized agent retrieve the fathom account that owns the api key, create a fathom event for a site, and create a fathom milestone for a site. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Fathom Analytics account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Fathom Analytics capabilities.
Showing 12 of 15 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADRetrieve the Fathom account that owns the API key.
create_eventWRITECreate a Fathom event for a site.
INPUTS: site_id / name
create_milestoneWRITECreate a Fathom milestone for a site.
INPUTS: site_id / name / milestone_date
create_siteWRITECreate a Fathom site.
INPUTS: name / sharing / share_password / timezone
get_current_visitorsREADFetch the current visitor count and optional detailed breakdown for a Fathom site.
INPUTS: site_id / detailed
get_eventREADRetrieve a single Fathom event by site ID and event ID.
INPUTS: site_id / event_id
get_milestoneREADRetrieve a single Fathom milestone by site ID and milestone ID.
INPUTS: site_id / milestone_id
get_siteREADRetrieve a single Fathom site by site ID.
INPUTS: site_id
list_eventsREADList events for a Fathom site.
INPUTS: site_id / limit / starting_after / ending_before
list_milestonesREADList milestones for a Fathom site.
INPUTS: site_id / limit / starting_after / ending_before
list_sitesREADList Fathom sites available to the API key.
INPUTS: limit / starting_after / ending_before
run_aggregationWRITEGenerate a Fathom analytics aggregation report.
INPUTS: entity / entity_id / site_id / entity_name / aggregates
INPUT CONTRACTS
Know what the action needs before it runs.
create_event
site_idREQUIRED- The Fathom site ID used in the tracking code, such as CDBUGS.
nameREQUIRED- The event display name, up to 255 characters.
create_milestone
site_idREQUIRED- The Fathom site ID used in the tracking code, such as CDBUGS.
nameREQUIRED- The milestone display name, up to 255 characters.
milestone_dateREQUIRED- The milestone date in YYYY-MM-DD format. It must be before today.
create_site
nameREQUIRED- The website display name, up to 255 characters.
sharingOPTIONAL- The dashboard sharing configuration for the site.
share_passwordOPTIONAL- The password required when sharing is set to private.
timezoneOPTIONAL- The site's reporting timezone as a TZ database name.
get_current_visitors
site_idREQUIRED- The Fathom site ID used in the tracking code, such as CDBUGS.
detailedOPTIONAL- Whether to include top content and referrer breakdowns.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Retrieve the Fathom account that owns the API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountControl Create Event
Create a Fathom event for a site. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_eventVerify with Get Current Visitors
Fetch the current visitor count and optional detailed breakdown for a Fathom site. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_visitorsSAFETY BOUNDARY
Operate Fathom Analytics with explicit limits
- Authorize Fathom Analytics with API key and grant only the provider access required by the selected actions.
- 7 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Fathom Analytics rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Fathom Analytics task completed successfully.
CONNECTION MODEL
API key
Fathom Analytics API token used with the Authorization: Bearer <token> header. Create one from Settings > API at https://app.usefathom.com/api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 7
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Fathom Analytics.