Pirsch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PIRSCH_BASE_URL | No | Pirsch API base URL | https://api.pirsch.io |
| PIRSCH_HOSTNAME | No | Hostname passed to the SDK; unused by reads | localhost |
| PIRSCH_CLIENT_ID | Yes | Pirsch OAuth client ID | |
| PIRSCH_DOMAIN_ID | No | Default domain ID; otherwise pass domainId | |
| PIRSCH_TIMEOUT_MS | No | Positive request timeout in milliseconds | 5000 |
| PIRSCH_CLIENT_SECRET | Yes | Pirsch OAuth client secret |
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 |
|---|---|
| pirsch_get_domainA | Return the Pirsch SDK's default domain. Dashboard-scoped clients return their dashboard domain. Account-scoped clients may have additional domains and should select one explicitly for statistics queries. |
| pirsch_list_domainsA | List every Pirsch domain available to the configured OAuth client. Returns safe domain summaries for selecting domainId in statistics queries. |
| pirsch_query_statisticsA | Read Pirsch Analytics v1 statistics for a domain and date range. Pass domainId from pirsch_list_domains to query a specific domain. Supports traffic, pages, events, acquisition, devices, geography, tags, keywords, and funnels. |
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 3 tools
Each tool has a clearly distinct role: get_domain returns the default, list_domains enumerates available domains, and query_statistics fetches analytics. No overlap or ambiguity exists.
All tool names follow a consistent pattern of 'pirsch_' prefix plus a verb_noun structure (get, list, query). This makes the API predictable and easy to understand.
Three tools is well-scoped for an analytics server: domain discovery, default selection, and statistics querying. Each tool is necessary and there is no bloat.
The tool surface fully covers the workflow of selecting a domain and querying comprehensive statistics (traffic, pages, events, etc.). No obvious missing operations or dead ends exist for the stated purpose.