TRaX Docs
guides

Connect an AI agent (hosted MCP)

TRaX runs a hosted Model Context Protocol (MCP) server so you can point an AI agent — Claude, or any MCP-capable client — straight at the TRaX developer API. The agent gets one tool per /v1 operation: list your studios, add sources and destinations, read stream status, go live and go offline, send chat, list connections, and start a media upload — all as first-class tool calls, generated from the OpenAPI so they stay in step with the API.

No SDK to install and no glue code: connect the endpoint, present your credential, and the agent can operate your account.

Endpoints

Environment URL
Dev preview https://mcp-dev.traxstreaming.live

The gateway is a dev preview — connect to mcp-dev.traxstreaming.live. A production host on mcp.traxstreaming.live is not live yet; this page will list it once it is.

The server speaks the MCP streamable-HTTP transport over TLS.

Connect with Claude Code

Read-only tools (the API reference and OpenAPI browser) need no credential:

claude mcp add --transport http trax https://mcp-dev.traxstreaming.live

To let the agent act on your account, pass your credential as a Bearer header. It is forwarded to the API on your behalf and scoped to you:

claude mcp add --transport http trax https://mcp-dev.traxstreaming.live \
  --header "Authorization: Bearer sk_live_your_key_here"

Any MCP client works the same way — configure an HTTP MCP server at the URL above and set an Authorization: Bearer <token> header.

Authentication

The gateway accepts the same two credentials as the Developer API:

  • an API key (sk_live_…), provisioned for you by the TRaX team; or
  • an interactive-login access token (a user JWT from an OAuth Authorization-Code + PKCE sign-in) — the native-app path.

Your token is forwarded to the API and never stored or logged by the gateway. Every call is scoped to you: you only ever see and change your own studios.

What the agent can do

Once connected, the agent sees:

  • Reference tools (no credential): browse the OpenAPI, list endpoints, read a specific endpoint, and search the developer guides.
  • API tools (v1_…, one per operation): read tools (list studios, sources, destinations, stream status, chat messages, connections, media) and write tools (create a studio, add a source or destination, go live / go offline, send a chat message, start a media upload).

Read tools are marked read-only. Write tools are marked as such, and go-live / go-offline are highlighted as consequential so an agent asks before it acts.

Safety notes

  • Writes require a credential. If the agent tries a write without a token, the call is rejected with a clear message — nothing happens on your account.
  • Least privilege. Give the agent a key scoped to what you want it to do, and revoke it from the API Keys screen when you're done.
  • Availability. The developer API is a dev preview; treat it as evolving.

See also