Skip to main content
No MCP tools are registered in the current release. New sign-ins cannot approve a usable permission set yet.

​
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. When tools are available, Tars asks the member to choose an organization, resources and allowed permissions. Approval stays within that member’s permissions. The current empty tool catalogue means this release cannot complete a useful new connection. No agent editing, search or reporting tool is available.

​
Permissions available today

None. The API permission catalogue describes potential access, but MCP permissions are offered only when a registered tool uses them.

​
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 only the required permissions. You can also call the HTTP API directly. An API key does not add missing MCP tools.

​
Disconnect

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