Connect a compatible client
The public Streamable HTTP MCP endpoint is https://engage.shuffll.com/mcp. The documented connection uses an authorized Engage key in a private authorization header. The chosen client must support that connection method.
Client compatibility depends on the specific setup path. Do not treat an MCP endpoint as a directory listing or assume an OAuth-only client can use a private-header connection. Confirm the current authentication and client requirements in the public documentation.
Discover first, then act
After connecting, let the client initialize the protocol and discover the permitted tools. Begin with a read-only operation, such as inspecting available templates. Plan the workflow from the tools and capabilities returned for that workspace.
For a generation workflow, keep campaign setup, recipient preparation, the explicit generation action and result inspection distinct. A request to create a campaign does not itself establish that video was generated or that anyone received a message.
Use the right interface for each step
MCP and REST are two interfaces to documented Engage operations, not separate product tiers with different implicit capabilities. The current documented V1 workflow is fixed-video; a conversational request does not unlock unsupported personalization or delivery operations.
Use MCP for an assistant-driven workflow and REST where your application should control the sequence. Workspace export notifications can inform another system when rendering milestones occur; those are described in the export webhook guide.
QUESTIONS, WITH CONTEXT
Go one question deeper.
Explore the details that matter for this part of the workflow.
MCP setup and compatibility
Connect through the method the chosen client supports.
What is the public Engage MCP server address?
Use https://engage.shuffll.com/mcp for Streamable HTTP MCP. It is separate from the REST operation URL; do not append REST paths to it.
What does a compatible MCP client need?
The documented setup requires a client that can send the authorized Engage key through a private HTTP header. Check the exact connection path offered by the client and the current Engage authentication documentation before configuring it.
Does MCP availability mean there is an approved marketplace app?
No. Endpoint availability, client compatibility, directory submission, marketplace approval and a live listing are different facts. This guide does not establish marketplace approval or a working OAuth-only installation path.
Assistant operations
Give the assistant a supported task and inspect its result.
What is a useful first request after connecting an assistant?
Start with a read-only request such as discovering permitted templates or inspecting capabilities. That confirms the available tool surface without generating media or advancing a campaign.
Can a prompt bypass an unsupported API capability?
No. MCP uses permitted documented operations and the same release boundaries. The current fixed-video V1 contract does not gain video personalization, full template authoring or message sending because an assistant is making the request.
Should I explicitly ask the assistant to generate video?
Yes. Keep generation distinct from campaign setup and recipient preparation. An explicit generation request makes the intended operation clear; afterward, inspect the job and resulting media rather than assuming the action finished successfully.
This guide describes workspace capabilities and documented implementations. Availability depends on deployment, workspace configuration and the integration contract. Confirm the required features for your rollout with Shuffll.
Public API + MCP documentation ↗