Bring Web Analytics
to Cursor
Learn how to connect Pirsch Analytics to Cursor and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Pirsch Analytics MCP Server?
Connect Pirsch Analytics to your AI agent to monitor your website traffic and user behavior without compromising privacy. This MCP server allows you to collect data and query complex statistics through natural language.
What you can do
- Traffic Monitoring — Retrieve overview, visitor, and page statistics for any of your domains using specific date ranges.
- Event Tracking — Send individual or batch hits and events to track user conversions and interactions in real-time.
- Domain Management — List all configured domains and create new ones directly through the API.
- Referrer & Source Analysis — Analyze where your traffic is coming from with detailed referrer and UTM source statistics.
- Real-time Insights — Access active visitor counts and goal completion metrics to stay on top of your site's performance.
How it works
- Subscribe to this server
- Enter your Pirsch Access Token (Client Secret)
- Start querying your analytics from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Marketing Managers — get instant reports on campaign performance and visitor trends without opening a dashboard.
- Developers — integrate tracking hits and events into automated workflows or check site health from the CLI/IDE.
- Data Analysts — extract raw statistics and overview metrics for custom reporting and performance audits.
Built-in capabilities (14)
Create a new domain
Get active visitors statistics
Get events list statistics
Get conversion goals statistics
Get overview statistics for a domain
Get page statistics
Get referrer statistics
Get UTM source statistics
Get visitor statistics
List all domains
Send an event to Pirsch
Send a batch of events
Send as much information as possible for accurate analytics. Send a page view (hit) to Pirsch
Send a batch of page views (hits)
Why Cursor?
Cursor's Agent mode turns Pirsch Analytics into an in-editor superpower. Ask Cursor to generate code using live data from Pirsch Analytics and it fetches, processes, and writes. all in a single agentic loop. 14 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Pirsch Analytics in Cursor
Pirsch Analytics and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Pirsch Analytics to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Pirsch Analytics in Cursor
The Pirsch Analytics MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 14 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Pirsch Analytics for Cursor
Every tool call from Cursor to the Pirsch Analytics MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I get a quick summary of my website's performance for a specific period?
You can use the get_statistics_overview tool. Just provide the Domain ID and the start/end dates (YYYY-MM-DD). The agent will return key metrics like visitors, views, and bounce rate.
Is it possible to track custom user actions like button clicks?
Yes! Use the send_event tool. You'll need to provide the event name, the current URL, and visitor details (IP and User-Agent) to record the interaction in Pirsch.
Can I see which pages are the most popular on my site?
Absolutely. Use the get_statistics_page tool with your Domain ID and date range. It will list the top pages along with their respective view counts and visitor data.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Railway
10 toolsEquip your AI with direct access to your Railway infrastructure — manage projects, deployments, services, and environment variables.
LinkAce
9 toolsManage your bookmarks, tags, and collections via the LinkAce REST API.
Emarsys
10 toolsEquip your AI agent to manage email campaigns, track contact lists, and monitor automation programs via the Emarsys API.
Salesforce Marketing Cloud
6 toolsManage campaigns, track member engagement, measure marketing ROI, and optimize lead generation through natural conversation.