Jolt MCP

Jolt MCP gives compatible AI clients read-only access to your aggregate website and product analytics. Ask questions about traffic, events, breakdowns, trends, or conversion funnels without copying dashboard data into a conversation.

Connect an MCP client

Add the remote server URL below to a client that supports Streamable HTTP and OAuth. The client opens Jolt in your browser, where you sign in and choose the exact projects it may query. No API key is needed.

Clients that use a JSON MCP configuration can use this equivalent server entry. Menu names differ between clients, so consult your client’s instructions for adding a remote MCP server.

Only approve a connection you started. A localhost callback is normal for some desktop clients, but Jolt highlights it so you can verify that the request came from software on your computer.

Available analytics tools

• list_projects lists only projects approved for the current client.
• read_data_schema discovers tracked custom events and page paths before a query is written.
• get_overview summarizes visitors, pageviews, events, sessions, engagement, and visitors online now.
• get_timeseries shows how a metric changes over an hour, day, week, or month interval.
• get_breakdown groups traffic by event, page, referrer, country, city, operating system, or UTM source.
• query_funnel measures ordered or strict funnels of two to eight page and custom-event steps.

For reliable answers, let the client list projects and read the project schema before asking for a report. Use the shortest useful date range and exact event names. Jolt defaults analytics queries to the last 30 days and limits unusually large requests.

Limits

• Standard reports default to 30 days and accept at most 366 days. Funnel reports accept at most 90 days.
• A funnel conversion window defaults to 14 days, cannot exceed 90 days, and cannot be longer than the report period.
• A time series returns at most 500 points and a breakdown at most 50 rows.
• Each OAuth client can make up to 60 requests per minute and 300 requests per hour for a Jolt user.

The read-only, aggregate-only beta is available on every plan. Blocked, inactive, or over-limit projects remain unavailable until their normal Jolt access is restored.

Access and privacy

MCP is read-only. It returns aggregate counts and never exposes raw event rows, visitor identifiers, session identifiers, usernames, or custom event properties. Every query checks both the projects you approved for the OAuth client and your current Jolt membership, so removing a team member or project permission takes effect immediately.

Project access can be changed or revoked under Settings → MCP. Revoking a client invalidates its Jolt authorization and removes access to every selected project. You can reconnect later and choose a new project set.

Build a funnel

Describe the ordered pageviews or custom events that form a conversion, such as signup_started, email_verified, and subscription_started. Jolt reports users reaching every step, conversion from the first and previous steps, and drop-off. Ordered funnels allow unrelated events between steps; strict funnels do not. The default conversion window is 14 days.

Troubleshooting

• If authorization fails, remove the Jolt server from the client, revoke the old connection in Settings, and connect again.
• If a project is missing, confirm that your account is still an owner or member, then update the client’s project access.
• If a funnel is empty, first run read_data_schema and check the exact event names and requested date range.