Skip to main content

PostHog MCP Server

Base URL: https://us.posthog.com

Category Analytics
Tools 618
Auth Bearer Token

Install

Quick Start (recommended)

BEARER_TOKEN=YOUR_BEARER_TOKEN \
SERVER_REGION=YOUR_SERVER_REGION \
uvx mcparmory-posthog

With pip

pip install mcparmory-posthog
BEARER_TOKEN=YOUR_BEARER_TOKEN \
SERVER_REGION=YOUR_SERVER_REGION \
mcparmory-posthog

MCP Client Configuration

Add to your MCP client config (e.g. Claude Desktop, Cursor, Codex):

{
  "mcpServers": {
    "posthog": {
      "command": "uvx",
      "args": ["mcparmory-posthog"],
      "env": {
        "BEARER_TOKEN": "YOUR_BEARER_TOKEN",
        "SERVER_REGION": "YOUR_SERVER_REGION"
      }
    }
  }
}

Credentials

Set the following environment variables (via MCP client env config, shell export, or .env file):

  • BEARER_TOKEN — Bearer token
  • SERVER_REGION — PostHog cloud region prefix. Use us for US Cloud (default) or eu for EU Cloud hosted in Frankfurt. (default: us)

Do not commit credentials to version control.


Run Locally

First, configure your credentials in .env (see Credentials above).

pip install -r requirements.txt
python server.py

Connect MCP Client

Edit .mcp.json and replace <SERVER_DIR> with the absolute path to this directory, then add to your MCP client configuration.

Example (if server is at /home/user/mcp-servers/posthog):

{
  "mcpServers": {
    "posthog": {
      "command": "python",
      "args": ["/home/user/mcp-servers/posthog/server.py"]
    }
  }
}

Docker

Pre-built image (recommended)

docker run -p 8000:8000 \
  -e BEARER_TOKEN=YOUR_BEARER_TOKEN \
  -e SERVER_REGION=YOUR_SERVER_REGION \
  ghcr.io/mcparmory/posthog:latest

Build from source

First, configure your credentials in .env (see Credentials above).

docker build -t posthog .
docker run -p 8000:8000 --env-file .env posthog

Before running, make sure ports 8000 are free.### MCP client config (Docker)

For Docker, use SSE transport in your MCP client config:

{
  "mcpServers": {
    "posthog": {
      "type": "sse",
      "url": "http://localhost:8000/sse"
    }
  }
}

Files

  • .env - Credentials and server configuration
  • .mcp.json - MCP client config template
  • Dockerfile - Container build
  • LICENSE - MIT license for this generated code
  • requirements.txt - Python dependencies
  • README.md - This file
  • server.py - MCP server entry point
  • _auth.py - Authentication handlers
  • _models.py - Request/response models
  • _validators.py - Input validation

Note: Files starting with . are hidden by default on macOS/Linux. Use ls -a in terminal or enable "Show hidden files" in your file manager to see .env and .mcp.json.


MCP Blacksmith
Generated by MCP Blacksmith · Quickstart docs · Report a bug

Metadata

Release files for mcparmory-posthog 1.0.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for mcparmory-posthog 1.0.5
File Interpreter ABI Platform
mcparmory_posthog-1.0.5-py3-none-any.whl Python 3 none any Details

Release files / mcparmory_posthog-1.0.5-py3-none-any.whl

Download URL mcparmory_posthog-1.0.5-py3-none-any.whl
Size 383.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cb3e4064dcc9c887452088cb91bf40426f25b2c4b78acb770d73318b303fd692
BLAKE2b-256 checksum
How to use checksums
83978d6bde17b30b01cf3355155635fadc55c41fe3aade57ec785b21fcfc8593
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.3

Security for mcparmory-posthog 1.0.5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page