@vskstudio/takt-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAKT_ORG | No | Default organization slug for list_sites when none is provided. | |
| TAKT_API_KEY | Yes | API key (sent as a Bearer token). | |
| TAKT_BASE_URL | Yes | Base URL of your Takt instance, e.g. https://takt.example.com. |
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 |
|---|---|
| list_sitesA | List the sites (domains) in an organization. Requires a key with the sites:read permission. |
| get_summaryA | Top-line metrics for a site over a period: unique visitors, sessions, pageviews, bounce rate, average visit duration. Set compareToPrevious to also get the previous period figures. |
| get_timeseriesB | Time series of visitors and pageviews for a site, bucketed by hour or day. |
| get_breakdownB | Top values of a dimension for a site (e.g. top pages, traffic sources, countries, devices, browsers). |
| get_realtimeA | Number of visitors active on a site in the last 5 minutes. |
| get_goalsB | Conversions per goal for a site. Requires a key with the stats:read permission. |
| get_funnelsC | Funnel reports (step-by-step conversion) for a site. Requires a key with the stats:read permission. |
| get_revenueB | Revenue grouped by currency for a given revenue event on a site. |
| list_event_propertiesC | List the custom property keys recorded for a given event on a site. |
| get_property_breakdownC | Break down a custom property of an event by value (e.g. counts per plan for a Signup event). |
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 10 tools
Each tool targets a distinct analytics metric or resource (funnels, goals, revenue, realtime, etc.). Despite many 'get_' prefixed tools, the descriptions clearly differentiate their purposes, leaving no ambiguity for an agent.
All tool names follow a consistent verb_noun pattern in snake_case with 'get_' for data retrieval and 'list_' for enumeration. This creates a predictable and easy-to-understand naming convention.
With 10 tools, the server is well-scoped for its purpose of providing analytics data. The count covers essential metrics without being excessive or sparse.
The tool set covers core analytics needs: top metrics, breakdowns, funnels, goals, revenue, realtime, time series, and property listing. Minor gaps exist, such as no tool for filtering or segmentation, but the core retrieval functionality is comprehensive.