Skip to main content
Telara

MCP Clients / Overview

Connecting AI Clients

Telara's supported employee connectors use OAuth 2.1 with PKCE. Employees select the approved connector and sign in once; Telara applies their organization's access and action policies on every request.

Streamable HTTP
OAuth 2.1 + PKCE
MCP Protocol

How It Works

One connection for governed work

A supported platform presents Telara in its directory, marketplace, or approved enterprise catalog. The employee selects Telara, completes OAuth once, and works with the same governed tools in the assistant they already use.

01
Select Telara

Choose Telara from the AI platform’s approved directory, marketplace, or organization catalog.

02
Sign in once

Complete OAuth 2.1 with PKCE using your work identity. You never paste an API key, client secret, tenant ID, or MCP configuration.

03
Search and do approved work

Your platform receives the Telara tools permitted by your organization and policy. Ask it to investigate company context or perform approved work.

04
Actions use your policies

Any write actions (create issue, send message, etc.) are checked against your permission policies. Actions set to "require approval" pause for human review.

Connector contract
TransportStreamable HTTP MCP
AuthenticationOAuth 2.1 + PKCE + dynamic client registration
PolicyEmployee, organization, tool, and action policy evaluated on every request

Coding Agents

IDE tools and coding agents

AI-powered IDEs and coding agents. Prefer the approved marketplace or organization deployment path for employee use rather than copying a server URL or credentials.

Agent Frameworks

Agent frameworks

Python and JavaScript frameworks for building custom AI agents. Connect Telara as a tool provider in a few lines of code using each framework's MCP adapter.

Transport

SSE transport

All supported clients use SSE (Server-Sent Events) to stream tool results from Telara. SSE is a persistent HTTP connection — your tool connects once, and Telara streams responses back in real time as your agent calls tools.

Why SSE
Works over standard HTTP — no special firewall or proxy rules needed
Streams incremental results as the agent works
Natively supported by all major MCP client libraries
Requirements
Outbound HTTPS access to api.telara.dev on port 443
A work identity permitted by your organization's Telara policy
At least one data source configured in your configuration