Skip to content
Thirdlane

AI Agents and Partners

Thirdlane is designed to be driven by AI agents and third-party platforms, not just human administrators. Agents can make and control calls, send messages, and pull data through the same REST API described in this section - and, increasingly, through a dedicated agent-friendly interface.

Model Context Protocol (MCP)

The Model Context Protocol is an open standard that lets AI agents call external tools. Thirdlane provides an MCP server that exposes the platform’s Actions and Reporting as ready-made tools, so an agent (in Cursor, Claude Desktop, or your own framework) can operate the PBX without bespoke integration code.

The MCP server is a thin adapter over the REST API:

  • It holds no business logic - every tool calls a Thirdlane REST endpoint with a scoped API key, and all authentication, tenant scoping, and validation stay in the platform.
  • It resolves per-plane base URLs at runtime from the discovery endpoint, so it keeps working as planes move to separate servers.

Tools

Read-only tools are always available: discover service planes, query CDR, and list or fetch recorded calls.

Write tools - place a call, send a message, hang up, transfer, and start/stop recording - are registered only when explicitly enabled. Keeping them out of the tool list unless enabled means an agent cannot even see call or message capabilities unless the operator has opted in.

  • Use a dedicated, tenant-scoped API key for each agent so its reach is limited and independently revocable.
  • Enable write tools only for agents that need to take action; leave them read-only otherwise.
  • Prefer per-integration keys so you can audit and revoke one agent without affecting others.

Partner integrations

Partners such as contact-center and voice-AI providers integrate at two layers:

  • REST + MCP for control and data - originate and transfer calls, send messages between users, and pull reporting.
  • SIP for media - an AI agent or partner service can register as a SIP endpoint to receive and place calls and to participate in warm transfers. See Special Endpoints for registering SIP credentials.

Because every cross-plane reference is a fully-qualified address resolved from the discovery endpoint, partner services always know exactly which server to reach for calling, messaging, and media.

Roadmap

This area is evolving quickly. Planned additions include realtime Telemetry (active calls, presence, queue/agent status), event subscriptions, and deeper Connect integration (agent identities, direct messaging, and screen-pop on transfer).