:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
import type { Schemas } from '@/api/generated'
import { MCPToolResultError } from '@/lib/errors'
import type { Context } from '@/tools/types'
export type McpToolResult = Schemas.MCPToolResponse
/**
* Invoke an MCP tool via the PostHog API.
*
* Goes through `context.api.request` rather than calling `fetch` directly. That is the seam a
* re-routed client overrides (see lib/connection-forwarding.ts), so a tool built on this reaches
* whichever project its context points at without the caller's bearer token ever going anywhere the
* client did not build itself. It also picks up the shared 429 retry policy and the typed error
* mapping (`PostHogRateLimitError`, `PostHogPermissionError`, `PostHogValidationError`) that error
* classification reads.
*
* @param context - The MCP context containing API client and state
* @param toolName - Name of the MCP tool to invoke (e.g., 'execute_sql')
* @param args - Arguments to pass to the tool
* @returns The tool result with success status and content
*/
export async function invokeMcpTool(
context: Context,
toolName: string,
args: Record<string, any>
): Promise<McpToolResult> {
const projectId = await context.stateManager.getProjectId()
const result = await context.api.request<McpToolResult>({
method: 'POST',
path: `/api/environments/${projectId}/mcp_tools/${toolName}/`,
body: { args },
})
if (!result.success) {
throw result.error_type
? new MCPToolResultError(result.content, result.error_type, result.error_code ?? undefined)
: new Error(result.content)
}
return result
}