@datafast/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATAFAST_API_KEY | Yes | Your DataFast API key (starts with `df_`) | |
| DATAFAST_BASE_URL | No | API base URL (defaults to `https://datafa.st`) | https://datafa.st |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_overviewB | Get high-level analytics metrics including visitors, sessions, bounce rate, average session duration, revenue, revenue per visitor, and conversion rate. Returns aggregate data for the specified time period. |
| get_timeseriesB | Get time series analytics data with configurable intervals (hour, day, week, month). Returns visitors, sessions, revenue, and conversion rate over time. Great for trend analysis and charts. |
| get_pagesA | Get the most visited pages on the website, ranked by visitor count. Includes hostname, path, visitor count, and revenue attribution per page. |
| get_referrersA | Get the top traffic referrers (sources linking to the website). Includes referrer URL, visitor count, and revenue attributed to each referrer. |
| get_countriesA | Get visitor counts and revenue broken down by country. Returns country name, flag image URL, visitor count, and revenue. |
| get_citiesA | Get visitor counts and revenue broken down by city. |
| get_regionsC | Get visitor counts and revenue broken down by region/state. |
| get_browsersB | Get visitor counts and revenue broken down by web browser (Chrome, Safari, Firefox, etc.). |
| get_devicesB | Get visitor counts and revenue broken down by device type (desktop, mobile, tablet). |
| get_operating_systemsB | Get visitor counts and revenue broken down by operating system (Windows, macOS, iOS, Android, Linux, etc.). |
| get_campaignsA | Get visitor counts and revenue broken down by UTM campaign parameters (source, medium, campaign, term, content). Great for measuring marketing campaign performance. |
| get_goalsA | Get custom goal completion data including goal name, number of completions, and unique visitors who completed each goal. |
| get_hostnamesA | Get visitor counts and revenue broken down by hostname (useful for multi-domain tracking). |
| get_realtimeA | Get the number of visitors currently active on the website in real time. |
| get_realtime_mapA | Get real-time visitor data with geographic coordinates for map visualization. Includes recent events, recent payments, and conversion predictions. |
| get_metadataA | Get metadata about the tracked website including domain, timezone, name, KPI settings, and currency configuration. |
| get_visitorA | Get detailed information about a specific visitor including their identity (country, browser, device), activity (visit count, page views, goals completed), and conversion predictions. |
| track_goalB | Track a custom goal completion for a specific visitor. Goal names must be lowercase, alphanumeric with underscores/hyphens, max 64 characters. |
| delete_goalsA | Delete goal events. Filter by date range, visitor ID, or goal name. At least one filter must be provided. |
| track_paymentA | Track a payment event for revenue attribution. Links payments to visitors for conversion tracking. |
| delete_paymentsA | Delete payment events. Filter by transaction ID, visitor ID, or date range. At least one filter must be provided. |
| identify_visitorB | Link a DataFast visitor to a user in your system. Associates the visitor ID with a user ID and optional metadata for enriched analytics. |
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 22 tools
Most tools are clearly distinct, especially the get_* breakdowns which explicitly name their dimension (country, city, browser, etc.). Minor confusion could arise between get_realtime and get_realtime_map, but their outputs differ enough. The large family of similar analytics tools requires careful reading, but names and descriptions mitigate ambiguity.
All tool names follow a consistent lowercase_with_underscores pattern using verb_noun: get_* for retrievals, track_* for event creation, delete_* for deletions, and identify_visitor for association. This is highly predictable and consistent across the entire set.
At 22 tools, the server is on the heavier side but the count is justified by the wide range of analytics dimensions (countries, cities, browsers, devices, etc.) plus tracking and deletion operations. It exceeds the ideal 15-tool range but does not feel bloated for an analytics platform.
The analytics surface is broad, covering many breakdowns and real-time data. However, there are notable gaps: no get_payments to read payment events despite having delete_payments, and no list/search for visitors beyond fetching a single visitor by ID. These missing read operations create dead ends in the tracking lifecycle.