Skip to content
txcast txcast txcast docs

Connect Claude Code

Store the credential

Section titled “Store the credential”
Terminal window
export TXCAST_AGENT_TOKEN='txc_REDACTED'

Do not write the resolved token into a tracked file.

Add .mcp.json

Section titled “Add .mcp.json”
{
    "mcpServers": {
        "txcast": {
            "type": "http",
            "url": "https://api.txcast.com/mcp",
            "headers": {
                "Authorization": "Bearer ${TXCAST_AGENT_TOKEN}"
            }
        }
    }
}

Claude Code asks whether to trust a project-scoped server. Inspect the file and accept only when the project is trusted. Run claude mcp list or use /mcp to inspect connectivity.

Configure tool permissions so sensitive writes require confirmation. Credential scopes remain enforced even if local prompts are relaxed.

Verify safely

Section titled “Verify safely”

Start with a read-only request:

Read the txcast context and explain which workflows I can see. Do not call mutation tools.

If tools do not appear, check the environment variable, bearer expiry, scopes, current seat, and MCP connection status.

A shell claude mcp add --transport http --header … command may persist the expanded header in local configuration. Prefer the environment-variable form when token-at-rest handling matters.

See the official Claude Code MCP guide for current configuration scopes and permission controls.