Skip to main content
Telara

Connect / Claude

Connect Claude to Telara

Once Telara is listed in Claude’s Connectors Directory, an employee can add it from Claude and sign in once. Telara then applies the same organization-approved policy used for every other client.

client_type: claude

The endpoint

Streamable HTTPhttps://api.telara.dev/v1/mcp
AuthOAuth 2.1 + PKCE with dynamic client registration

Connect it yourself

The public path is one click in Claude’s Connectors Directory followed by your normal Telara sign-in. Directory submission is pending access to a qualifying Anthropic Team or Enterprise organization; do not treat an unlisted custom connector as the public deployment path.

1
In Claude, open Search and tools, then Add connectors, and select Telara when it is available in the directory.
2
Choose Connect. Sign in when Telara opens the authorization page; OAuth 2.1 with PKCE completes without an API key, MCP URL, client secret, or tenant setup.
3
Ask a question only your authorized company data can answer, then confirm the Telara audit event.

Rolling it out centrally

The directory provides consistent discovery. It does not bypass Telara or source-system permissions.

1
Use Claude Team or Enterprise controls to make the approved Telara directory connector discoverable to the right employees.
2
Each employee still completes their own sign-in; Telara resolves that employee’s organization membership and policy at authorization time.

Before you commit to this

A connector listing is not a blanket grant

Installing or discovering Telara does not grant access to every company system. Telara evaluates the employee, organization, requested tool, and action against policy for each request.

Confirm it actually worked

The client's “connected” badge reports a successful handshake, not a tool call. Ask Claude something answerable only from your indexed Telara data, then read GET /v1/mcp/audit/log and look for a row with client_type=claude.

An answer with no matching audit row means the assistant replied from its own knowledge and never called Telara — a routing problem in the tool descriptions, not a broken connection. Every transport check will still look green.

Support, privacy, and reviewer testing

The complete OAuth and platform-review guide defines the governed 21-tool contract, the reviewer test flow, and the safe test action for platforms that permit writes.

For setup or reviewer access, contact support@telara.dev. For privacy requests, contact privacy@telara.dev. Telara's Privacy Policy and Terms of Service apply to every connection.

Comparing platforms? See connection paths for what each one needs. Looking instead to let Telara readthis platform's usage and spend? That is the opposite direction — see the connector catalog.