MCP compatibility
Understand the boundary between legacy MCP connections and the current REST API.
MCP lets an assistant discover and call tools. The current creative app implements its new public contract as the REST API, with workspace keys and credit billing.
The app also contains optional forwarding for older MCP and OAuth routes. Those connections depend on a separately configured compatibility service. They are not a native MCP wrapper around every new creative API endpoint.
Choose an integration
For a new integration, start with the REST quickstart. For an existing MCP client, use the connection details supplied for that service and confirm its current authentication and tool list.
Do not assume changing an older API hostname or replacing its key with a new vb_live_ key is enough to migrate an MCP client.