Skip to main content
The Tars MCP server lets an AI tool read your organization’s analytics. It offers five read-only tools. They cannot change anything in Tars, and they cannot read live chat or conversation transcripts. MCP connections are available on paid plans.

Server URL

Copy MCP server URL from Settings → Integrations → MCP connections, or from Profile → MCP connections. The regional server URL ends in /mcp. Use the displayed value so sign-in reaches the correct region.

Signing in from an AI tool

Claude, Cursor and other MCP clients accept a remote server URL. Add the displayed URL and choose the client’s sign-in action. Tars then asks the member to choose an organization under Workspace, the resources to share and the permissions to allow. Allow access completes the sign-in. Approval stays within that member’s permissions. An organization on the Free plan shows MCP connections are available on paid plans.

Permissions

The sign-in offers one permission, Read analytics (analytics:read). It covers the whole organization, so it needs access to all resources. See Authentication.

Tools

Date formats

Each pipe that analytics_query reads takes its dates in one of two formats. analytics_pipes with pipe set lists each parameter with its type. A pipe with Date parameters counts whole days, and date_to includes its day:
Some pipes take DateTime values in date_from and date_to. Their window ends at date_to itself, not at the end of that day. They are reply_latency, reply_breakdown, human_report, whatsapp_messages, csat_summary, campaign_funnel, campaign_funnel_trend, conversation_flow, conversation_list and conversation_ai_cost. To include October 31, pass 2026-11-01 00:00:00 as date_to. With raw_window set to "1", a pipe reads an exact window from DateTime values in date_time_from and date_time_to. These pipes accept it: results_summary, results_trend, sources_breakdown, busiest_times, journey_funnel, tool_calls_summary, topic_report_card, need_report_card, topic_report_readiness, component_summary and component_options. Without it, they count whole days from date_from and date_to. analytics_pipes lists each pipe’s parameters and their types. reply_breakdown and human_report also compare two periods. previous_from starts the period to compare against. date_from starts the current period:
If you leave out previous_from, it starts on 2026-01-01 00:00:00. That start can make the window too large, so always pass it.

Limits

  • analytics_query returns at most 500 rows, 100 by default. When truncated is true, narrow the date window or the filters.
  • A date window can be at most 366 days. For reply_breakdown and human_report, the window runs from previous_from to date_to, so it includes the comparison period.
  • A response holds about 200 KB of rows at most. Larger results are cut and marked truncated.
  • Tool calls use the read rate class. See Requests.

Errors

When the parameters are wrong, the tool call fails with invalid_input and a reason you can act on. Fix the parameters and call again. For example, a window that is too large returns this reason:
A pipe that rejects a parameter also returns invalid_input, with the reason from the pipe. Too many analytics reads return rate_limited with the time to wait before a retry. Other failures return internal_error.

Manage connections

Admins can inspect organization connections in Settings → Integrations → MCP connections. Members manage their own connections in Profile → MCP connections. Connection access follows the member’s current role. Moving an organization to another region requires a new sign-in.

Use an API key instead

A client that supports custom authentication headers can use an API key with the displayed MCP server URL. Configure Authorization: Bearer tars_sk_… in the client’s server-side header settings. An admin creates a key with the Read analytics permission. See Authentication. You can also call the HTTP API directly.

Disconnect

Select a connection’s disconnect action to revoke access. Disconnecting stops that connection’s credentials.