APOB AI MCP

npx add-mcp 'https://backend.apob.ai/mcp'

MCP overview

Let an authorized AI agent create AI live streaming channels, propose scenes, vote, and use APOB's image and video tools through MCP.

APOB exposes a remote Model Context Protocol (MCP) endpoint at /mcp using Streamable HTTP. A connected client can discover tools for generation, models, elements, media transfer, live streaming channels and scenes, and billing. The server also provides a resource describing the required create_image prompt syntax.

Use tools/list to discover the tools available to your account and connection. Use resources/list to discover reference material available to your connection and resources/read to retrieve it. Resource use depends on the client.

Give your agent a live streaming workflow

Use Live streaming tools to create a channel from text or an accessible source, propose upcoming scenes, and vote on candidates. Start with a brief that makes duration, visibility, audience controls, and spending intent explicit:

Create a private AI live streaming channel showing a calm forest at sunrise.
Use P480 resolution and 15000 milliseconds of initial content.
Disable audience scene creation. Review the credit effects before submitting,
create the channel once, and save its channel ID and returned playback URL.
Report channel creation separately from verified playback readiness.

The current MCP Live surface is create_live_room, create_live_scene, and vote_live_scene. Channel reads, stopping, reopening, and audience-policy changes use the GraphQL API or APOB. Do not pass an MCP OAuth token to GraphQL; API authentication is separate.

[!NOTE]

A channel receipt or LIVE status confirms the channel's business state. Startup and playable HLS media are asynchronous. Save the channel ID and inspect the existing channel before repeating an uncertain write. A live channel is not a generation task for get_generation_result.

Connect your client

1. Obtain the MCP resource URL

Add https://backend.apob.ai/mcp as the production remote server URL. These examples use APOB_MCP_URL for that complete resource URL, including /mcp. Other environments use their own enabled endpoint.

2. Authorize the connection

Add the remote endpoint in an MCP client that supports Streamable HTTP and OAuth authorization code with PKCE. Sign in to APOB and review the account and client before approving mcp:access. See authentication.

3. Discover the current tools

Initialize the client, then request tools/list. Use the returned input schemas for your account. Some generation defaults change with the account's free or paid status and selected quality.

4. Submit once and follow the receipt

Check inputs, credits, and billing settings before a write. Save returned identifiers and follow the existing channel or task through its supported read interface. Acceptance is separate from playback, final media, payment, or entitlement fulfillment.

[!NOTE]

MCP uses an OAuth access token. GraphQL uses an APOB API key or Firebase ID token. An APOB API key, Firebase ID token, or browser session cookie does not replace the MCP bearer token.

Choose a reference

[card] Live streaming

Create an AI live streaming channel, propose scenes, and vote with exact tool inputs.

[card] First channel walkthrough

Choose a source and visibility, submit once, and check HLS playback.

[card] Authentication

Discover OAuth endpoints, authorize with PKCE, and manage connected apps.

[card] HTTP and JSON-RPC

Initialize, discover capabilities, call tools, and interpret errors.

[card] Tool catalog

Find tool contracts and understand account-specific defaults.

[card] Generation

Create, edit, clone, extend, and retrieve final media.

[card] Library and elements

Discover assets, train models, and manage reusable references.

[card] Uploads and imports

Transfer local files or import remote files for Live and generation inputs.

[card] Billing

Inspect offers and accounts, submit purchases, and follow Checkout status.

[card] Connected apps API

Retrieve setup instructions, list connections, and revoke access through GraphQL.

Account and task boundaries

Tool identity comes from the verified connection. Each call rechecks the account; knowing another account's identifier does not grant access to its private assets. Generation results are restricted to the owner of the root generation task.

Channel creation prepays initial generation. Paid scene proposals and votes can also spend credits; scene vote weight includes free votes and is not a spending total. See Live streaming for the distinct zero-credit scene and vote behaviors.

Creation and billing writes can spend credits or charge a saved payment method. Repeated writes can execute again. If a response is uncertain, reconcile the existing task, account history, or payment before considering another write. Read credits and billing before running paid work.

The setup instructions returned by the GraphQL API describe client configuration. Successful use also depends on the enabled endpoint and the client's transport and OAuth support.

This documentation is built and hosted on Mintlify, a developer documentation platform.