agents
The MCP server
Local stdio and remote Streamable HTTP with OAuth 2.1. One server, every client.
Last updated 2026-07-10
Two transports
| Transport | For | Auth |
|---|---|---|
| stdio (local) | Claude Code, Codex, Cursor, Desktop, CLIs | Device-style connect grant (browser approval) |
| Streamable HTTP (remote) | claude.ai connectors and hosted clients | OAuth 2.1: PKCE, dynamic client registration, short-lived tokens |
Beyond tools
- Prompts:
direct_a_video,ad_from_product_url,review_the_story, one-click story-first flows. - Resources:
cadenza://modes,cadenza://brands,cadenza://tools, browsable context so the agent is not calling blind. - Auto-connect: a tool call before linking returns a one-click approval URL instead of a dead error.
- Server instructions: the server tells the client when to plan, what is billable, and that publishing requires confirmation.
Safety and scopes
Connections carry scopes, least privilege is enforced server-side, and a mis-scoped key is refused. All safety policy applies identically to agent traffic.
Remote endpoint
The remote connector is live at https://mcp.cadenza.media/mcp (OAuth 2.1: dynamic client registration, PKCE, short-lived single-use codes). https://cadenza.media/api/mcp is the same server on the apex domain and keeps working for existing connections. Local stdio also works via npx cadenza connect.