Create Connector
Changed onRegister an MCP server. What happens next depends on auth_config.type.
For oauth2, Tavus performs discovery against the server and registers itself as a client (Dynamic Client Registration), then returns an authorize_url alongside the connector. Send the customer there; the server redirects back to Tavus, which stores the tokens and moves the connector to oauth_status: linked. Nothing needs to be registered on your side. If discovery or registration fails the connector is not created, so you can retry cleanly.
For every other type the connector is usable immediately.
Attach the connector to a PAL with layers.mcp.connectors; the in-call agent connects to the server and discovers its tools itself, so there is nothing to import.
Request
- Base URLhttps://tavusapi.com
- URLhttps://tavusapi.com/v2/connectors
- AuthAPI key in header x-api-key
Request body
Example request
{
"name": "Linear",
"server_url": "https://mcp.linear.app/mcp",
"auth_config": {
"type": "oauth2"
}
}Response
Connector created. For oauth2, also carries authorize_url and oauth_state.
Example response
{
"connector_id": "c8-58ea0f6420b2",
"owner_id": 4309,
"team_id": null,
"name": "Linear",
"source": "mcp",
"server_url": "https://mcp.linear.app/mcp",
"auth_config": {
"type": "oauth2"
},
"selected_tool_names": null,
"oauth_status": "linked",
"oauth_scopes": [
"read",
"write"
],
"access_token_expires_at": "2026-08-18T09:14:00",
"last_indexed_at": "2026-08-17T18:20:11",
"last_index_error": null,
"created_at": "2026-08-17T18:02:56.838918",
"updated_at": "2026-08-17T18:20:11.563911"
}Changes
- info
endpoint added
- info