Connect your agent

Bring the agent you already use.

Codex CLI and Claude Code are the first target clients. This page describes the token-based setup path. It does not describe OAuth, an install deep link, or a completed connection.

Before you connect

1. Sign in to the studio and select the workspace you intend to use.
2. When live token creation is available, create a named, expiring agent connection with only the required scopes. Keep the token in your secret manager or shell environment, out of prompts, URLs, recordings, and git.
3. Set CASTROOM_MCP_URL to the exact endpoint supplied by the studio and CASTROOM_TOKEN to that connection’s token. Launch the client from that environment.

Codex CLI

The installed codex-cli 0.169.0 accepts this command shape, checked with codex mcp add --help on 14 November 2026. Authenticated discovery against Faceful remains untested.

# Template only: the live URL and token issuer are pending.
# CASTROOM_TOKEN is supplied by your environment, never pasted here.
codex mcp add castroom \
  --url "$CASTROOM_MCP_URL" \
  --bearer-token-env-var CASTROOM_TOKEN

For manual configuration, merge this entry into your Codex configuration after the real endpoint is available. Replace only the URL placeholder; the token field names an environment variable.

[mcp_servers.castroom]
url = "REPLACE_WITH_STUDIO_PROVIDED_HTTPS_MCP_URL"
bearer_token_env_var = "CASTROOM_TOKEN"

Reference: official Codex MCP configuration.

Claude Code

The installed Claude Code 2.1.150 supports remote HTTP MCP configuration. Merge the following into a trusted project’s .mcp.json; do not overwrite existing server entries. The token stays in the environment.

{
  "mcpServers": {
    "castroom": {
      "type": "http",
      "url": "${CASTROOM_MCP_URL}",
      "headers": {
        "Authorization": "Bearer ${CASTROOM_TOKEN}"
      }
    }
  }
}

Start Claude Code from the configured environment, review the project server trust prompt, and inspect /mcp. Environment expansion is documented by Claude Code; a fresh authenticated Faceful trial is still pending. Reference: official Claude Code MCP setup.

Confirm the connection

When the backend is live, ask the agent to call studio_get_context. Check that it returns the intended workspace, actual capabilities, and the connection’s scopes. The studio must then show server-recorded last activity. Copying a command or seeing a server in local configuration is not a successful connection.

Read my Faceful workspace context. Tell me the available avatars,
connected accounts, current limits, and actions this connection allows.
Do not create or publish content.

First campaign request

After a successful context check, use concrete dates and named accounts. Resolve timezone ambiguity before preparing a schedule.

Using the supplied company brief, prepare three distinct avatar videos.
Use the workspace’s authorized presenter and brand rules. Draft a schedule
for 16, 18, and 20 November 2026 at 09:00 Europe/Athens on the connected
accounts I select. Show me the exact review manifest before publishing.

Other hosts

Other MCP clients are not tested. Streamable HTTP support alone does not establish authentication or workflow compatibility. Use your host’s official setup path and retain the same workspace scope and review requirements.

Read access, expiry, and revocation behavior