How do I create a PostHog Personal API Key?

Log in to [**PostHog**](https://app.posthog.com), click your profile icon > **Personal API keys**, then **+ Create a Personal API Key**. Give it a label, select the required scopes and copy the key immediately — it won't be shown again after page refresh.

Can I toggle feature flags via the agent?

Yes! Use `create_feature_flag` to add new flags, `update_feature_flag` to modify existing ones (name, description, enabled status), and `delete_feature_flag` to remove them. You'll need the numeric flag ID from `list_feature_flags` for update and delete operations.

What's the difference between events and persons?

**Events** are actions that happen in your product (pageviews, button clicks, purchases). **Persons** are the users who perform those actions, identified by distinct_id. Events are linked to persons, so you can see what actions a specific user has taken. Use `list_events` to browse activity and `get_person` to see a user's profile.

Can I use this with a self-hosted PostHog instance?

Yes! The tools default to `https://app.posthog.com` for the US cloud, but you can set the `host` parameter to your self-hosted instance URL (e.g. `https://posthog.yourcompany.com`). EU cloud users should set the host to `https://eu.posthog.com`.

PostHog Alternative MCP Server for CrewAI 13 tools — connect in under 2 minutes

Name: PostHog Alternative
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 13 Tools Framework

Connect your CrewAI agents to PostHog Alternative through Vinkius, pass the Edge URL in the `mcps` parameter and every PostHog Alternative tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="PostHog Alternative Specialist",
    goal="Help users interact with PostHog Alternative effectively",
    backstory=(
        "You are an expert at leveraging PostHog Alternative tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in PostHog Alternative "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 13 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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

About PostHog Alternative MCP Server

Connect your PostHog account to any AI agent and gain full control over your product analytics, feature flags and user cohorts through natural conversation.

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

What you can do

User & Project Discovery — Verify your account access and list all analytics projects
Feature Flag Management — List, create, update and delete feature flags with rollout configuration
Cohort Inspection — Review all behavioral cohorts and their filter definitions
Person Analytics — Look up individual users by distinct ID, view their properties and activity timeline
Event Tracking — Browse recent events, filter by event type and inspect event properties
Timeline Annotations — Create and review annotations that correlate metric changes with deployments or launches

The PostHog Alternative MCP Server exposes 13 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect PostHog Alternative to CrewAI via MCP

Follow these steps to integrate the PostHog Alternative MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 13 tools from PostHog Alternative

Why Use CrewAI with the PostHog Alternative MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with PostHog Alternative through the Model Context Protocol.

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

PostHog Alternative + CrewAI Use Cases

Practical scenarios where CrewAI combined with the PostHog Alternative MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries PostHog Alternative for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries PostHog Alternative, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain PostHog Alternative tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries PostHog Alternative against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

PostHog Alternative MCP Tools for CrewAI (13)

These 13 tools become available when you connect PostHog Alternative to CrewAI via MCP:

create_annotation

Annotations appear on insights graphs and help correlate metric changes with deployments, launches or incidents. Requires the content text. Optionally set a date_marker (ISO 8601 date). Create a new annotation in PostHog

create_feature_flag

Requires the flag key (unique identifier). Optionally set the name, description, enabled status, rollout percentage and filters. The key must be unique across all flags in the project. Create a new PostHog feature flag

delete_feature_flag

All targeting conditions, release conditions and experiment data associated with the flag will be deleted. Provide the numeric flag ID. WARNING: this action is irreversible. Delete a PostHog feature flag

get_feature_flag

Provide the numeric flag ID from list_feature_flags. Get details for a specific PostHog feature flag

get_person

Provide the distinct_id used to identify the person. Get details for a specific person in PostHog

get_user

Returns user ID, email, name, organization membership and permissions. Use this to verify your API key is working and check your access level. Get the current PostHog user details

list_annotations

Annotations are markers on timeline graphs that highlight important events like deployments, feature launches or incidents. Returns annotation ID, content, date marker and whether it is pinned. List annotations in PostHog

list_cohorts

Each cohort is a dynamic group of users defined by event-based or property-based filters. Returns cohort ID, name, description, whether it is calculated or static. List behavioral cohorts in PostHog

list_events

Optionally filter by event name (e.g. "pageview", "signup", "purchase") and set a limit. Each event includes the event name, timestamp, person distinct ID and properties. List events tracked in PostHog

list_feature_flags

Each flag has a key, name, enabled status, rollout percentage, filters and release conditions. Returns flag ID, key, name, whether it is active, and the targeting configuration. Use this to audit feature flag coverage. List all feature flags in PostHog

list_persons

Each person has distinct IDs, properties, creation date and last event timestamp. Optionally set limit (default 20) and offset for pagination. List persons (users) tracked in PostHog

list_projects

Each project is an analytics workspace with its own events, persons, feature flags and cohorts. Returns project ID, name, organization and creation date. List PostHog projects

update_feature_flag

Provide the flag ID and any fields to change: name, description, enabled status. Only the fields you provide will be updated. Update an existing PostHog feature flag

Example Prompts for PostHog Alternative in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with PostHog Alternative immediately.

"Show me all feature flags and which ones are enabled."

"Create an annotation for today's deployment of version 3.2.0."

"Show me the profile of user 'user_12345'."

Troubleshooting PostHog Alternative MCP Server with CrewAI

Common issues when connecting PostHog Alternative to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

PostHog Alternative + CrewAI FAQ

Common questions about integrating PostHog Alternative MCP Server with CrewAI.

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.

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.

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.

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.

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.