Ask your AI where users drop off after the click.
Trends, funnels and retention from your PostHog project, and read-only HogQL when the question needs it — answered inside ChatGPT, Claude, Codex or Cursor, next to the campaigns that sent those users. Connect PostHog to toolfare once; your AI reads it with your own login, and every read is free.
1Connect your AI app
Pick the app you use. You do this once, and every API on toolfare is then available in it.
Add toolfare as a connector in Claude
Add to Claudehttps://api.toolfare.ai/mcp
- 1Open Customize → Connectors and choose "Add custom connector".
- 2Paste this URL as the remote MCP server URL.
- 3Leave the OAuth client id and secret under Advanced settings empty.
- 4Complete the browser authorization, then return to your conversation.
Custom connectors are available on Free, Pro, Max, Team and Enterprise. A Free account may hold one custom connector in total.
Claude’s own instructions2What to ask
Copy a prompt into your AI app once you’re connected. It picks the right one of the 3 tools and tells you the price first.
Trends, funnels, retention and HogQL
Runs a read tool from PostHog’s MCP against your project — insight queries for trends, funnels and retention, validated read-only HogQL, and the data schema to write it against.
- “Where do users drop off between sign-up and first project?”
- “What is week-one retention for users who signed up last month?”
- “How many people triggered the checkout event yesterday?”
What your AI is allowed to ask PostHog
PostHog’s live MCP tool catalogue for your project, each tool marked as a read that runs or a change that would need review.
- “Which PostHog tools can you use through toolfare?”
- “Can you run SQL against our PostHog project?”
The PostHog projects your toolfare account can read
The projects you connected to toolfare, so a question runs against the right one.
- “Which PostHog projects are connected?”
- “Use our production project for this.”
1Create an API key
One key and one endpoint for every API on toolfare.
export TOOLFARE_API_KEY='tf_live_…'
2Every tool and its input
Send the tool name and its arguments as JSON; the reply is JSON too.
posthog_queryRuns a read tool from PostHog’s MCP against your project — insight queries for trends, funnels and retention, validated read-only HogQL, and the data schema to write it against.
posthog_list_toolsPostHog’s live MCP tool catalogue for your project, each tool marked as a read that runs or a change that would need review.
posthog_list_projectsThe projects you connected to toolfare, so a question runs against the right one.
Use it when
- You want to know what paid users did after they arrived, not just that they arrived.
- You want a funnel or retention curve without building the insight yourself.
- The question needs HogQL, and you would rather describe it than write it.
Look elsewhere when
- You want to create an insight, a feature flag or an annotation. Writes need review and are not available through the MCP connection.
- You want ad spend or CPA. PostHog does not know what you paid — that is your ad account. Use this instead
PostHog directly, or through toolfare
Directly
- The PostHog interface, or its own AI assistant
- A personal API key of your own
- Your own code to put product events next to ad spend
Through toolfare
- Ask in the chat you already use, in plain English
- One toolfare login; no PostHog key handed to an agent
- PostHog beside your ad accounts and revenue in the same question
You get reads, not PostHog. Nothing is saved as an insight or dashboard, no flag or annotation can be changed through the MCP connection, and nothing is monitored for you between questions.
Limits
- Only allowlisted read tools run; anything else is reported as needing review, and review is not reachable through the MCP connection.
- HogQL is validated as read-only before it runs, so a query that would modify anything is refused.
- Only projects you connected are readable; PostHog’s listing of every project in your PostHog account is not available.
