4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Pirsch Analytics MCP Server

Bring Web Analytics
to CrewAI

Learn how to connect Pirsch Analytics to CrewAI and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create DomainGet Statistics ActiveGet Statistics EventsGet Statistics GoalsGet Statistics OverviewGet Statistics PageGet Statistics ReferrerGet Statistics Utm SourceGet Statistics VisitorList DomainsSend EventSend Event BatchSend HitSend Hit Batch

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Pirsch Analytics

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

  1. Subscribe to this server
  2. Enter your Pirsch Access Token (Client Secret)
  3. 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_domain

Create a new domain

get_statistics_active

Get active visitors statistics

get_statistics_events

Get events list statistics

get_statistics_goals

Get conversion goals statistics

get_statistics_overview

Get overview statistics for a domain

get_statistics_page

Get page statistics

get_statistics_referrer

Get referrer statistics

get_statistics_utm_source

Get UTM source statistics

get_statistics_visitor

Get visitor statistics

list_domains

List all domains

send_event

Send an event to Pirsch

send_event_batch

Send a batch of events

send_hit

Send as much information as possible for accurate analytics. Send a page view (hit) to Pirsch

send_hit_batch

Send a batch of page views (hits)

Why CrewAI?

When paired with CrewAI, Pirsch Analytics becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Pirsch Analytics tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Pirsch Analytics in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Pirsch Analytics and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Pirsch Analytics to CrewAI 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Pirsch Analytics in CrewAI

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 CrewAI 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.

Pirsch Analytics
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Pirsch Analytics for CrewAI

Every tool call from CrewAI to the Pirsch Analytics MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →