Connect AI Tools to Robolly
Robolly's Model Context Protocol (MCP) server connects compatible AI assistants directly to your Robolly account. After connecting it, you can ask an assistant to browse your templates, import designs from the template gallery, create or update templates, and render images, PDFs, or videos.
The Robolly MCP server runs remotely, so there is nothing to download or host.
Before you start
You will need:
- A Robolly account with API access.
- An MCP client that supports remote Streamable HTTP servers and OAuth.
- Your Robolly API key from Account settings only when your client cannot use OAuth.
Use these connection details:
| Setting | Value |
|---|---|
| Server name | robolly |
| Transport | Streamable HTTP |
| URL | https://api.robolly.com/mcp |
| Authentication | OAuth (recommended) or API key |
Supported clients detect OAuth automatically and open Robolly in your browser. Sign in, review the organization the assistant may access, and approve the connection. Your Robolly API key is never shared with the client.
You can review and revoke OAuth connections at any time under Account settings → Connected AI Tools.
How to set up Robolly MCP in Claude Code
Run the following command in your terminal:
claude mcp add --transport http robolly --scope user https://api.robolly.com/mcp
Open /mcp in Claude Code and complete the browser sign-in. Run claude mcp list to confirm that Robolly is connected.
How to set up Robolly MCP in Codex
Add Robolly to your user-level MCP configuration and start OAuth sign-in:
codex mcp add robolly --url https://api.robolly.com/mcp
codex mcp login robolly
Complete the browser sign-in, then run codex mcp list to verify the connection.
How to set up Robolly MCP in VS Code
- Open the Command Palette.
- Run MCP: Add Server… and select HTTP.
- Enter
https://api.robolly.com/mcpas the URL androbollyas the name. - Complete the browser sign-in when VS Code connects.
Alternatively, add the server to your user-level mcp.json configuration:
{
"servers": {
"robolly": {
"type": "http",
"url": "https://api.robolly.com/mcp"
}
}
}
How to set up Robolly MCP in GitHub Copilot CLI
copilot mcp add --transport http robolly https://api.robolly.com/mcp
Complete the browser sign-in, then run copilot mcp get robolly to verify the connection.
How to set up other MCP clients
Configuration formats differ between MCP clients. For clients with OAuth support, use an HTTP server configuration without custom headers:
{
"mcpServers": {
"robolly": {
"type": "http",
"url": "https://api.robolly.com/mcp"
}
}
}
API key fallback
Clients that cannot use Robolly OAuth can still send the API key from Account settings as a Bearer token:
{
"mcpServers": {
"robolly": {
"type": "http",
"url": "https://api.robolly.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_ROBOLLY_API_KEY"
}
}
}
}
Your API key gives the connected assistant access to your Robolly organization. Keep it secret, use a secure input or environment variable when possible, and never commit it to source control.
Some clients call the transport type streamable-http instead of http. Both refer to the Streamable HTTP transport used by Robolly.
Available tools
| Tool | What it does |
|---|---|
list_templates | Lists templates in your Robolly organization. |
get_template | Gets a template, including its editable design. |
list_gallery_templates | Searches and lists designs available in the Robolly template gallery. |
create_template | Creates a new template, including importing a design from the gallery. |
update_template | Updates an existing template and its editable design. |
get_template_modifications | Lists base keys, detailed properties, value constraints, and examples accepted by a template. |
render | Renders a template as JPG, PNG, WebP, or PDF and returns a temporary file URL. |
render_video | Queues an MP4 or WebM video render with one or more clips, optional audio, and dynamic values. |
get_render | Checks a queued render's status and returns its temporary file URL when finished. |
The create_template and update_template tools change templates in your Robolly account. The render and render_video tools consume rendering credits in the same way as rendering through the dashboard or API.
Video rendering is asynchronous. After using render_video, the assistant can use the returned render ID with get_render until the render is finished. Video availability, duration, audio, and clip limits depend on your Robolly plan.
The MCP server does not currently expose template deletion.
Template names and previews
Refer to templates by their names when talking to the assistant. For example, ask it to render your Abrasive Open graph template instead of finding and pasting its template ID. The assistant uses list_templates to resolve the name to the ID required by Robolly's tools. If multiple templates have the same name, the assistant may ask you which one to use.
Template listing and lookup tools return each available previewUrl and an MCP resource link. When you ask to see previews, the tools instruct the assistant to use those URLs as inline Markdown images. This reuses existing previews and does not render new images.
Whether previews appear embedded ultimately depends on the MCP client. MCP resource links provide URLs but do not require clients to display them inline. Clients without inline remote-image support can still show or open the returned preview URL.
Dynamic and detailed modifications
Every named template element has a base modification key. Using the element name by itself changes its primary value. For example, title changes a text element's content, photo changes an image source, and shape changes a rectangle's color.
Detailed modification keys change a specific property by using the syntax {element-name}.{modification-key}. For example:
| Modification | Example key |
|---|---|
| Change a text color | title.textColor |
| Change an element's background | hero.background.color |
| Change opacity | photo.opacity |
| Change a filter value | photo.filters.0.value |
| Move an element | logo.x and logo.y |
The complete base key list and detailed modification guide come from the accepted-modifications endpoint and are returned by get_template_modifications. Each element includes concrete detailed keys based on its type and existing design structure. For example, filter and gradient-stop keys are returned only for indexes that already exist. The get_template response contains only template data, keeping the API resource and MCP workflow metadata separate.
Detailed modification keys apply while rendering through render or render_video. To permanently change the saved design, the assistant must use update_template instead.
Example prompts
After connecting the server, try prompts like:
- "Show me my 5 most recently updated Robolly templates. For every template with a
previewUrl, display an inline Markdown image using the exact URL, followed by its template name. Do not render new images." - "Find a certificate design in the Robolly template gallery and import it into my account."
- "Which fields can I modify when rendering my
Abrasive Open graphtemplate?" - "Render my
Abrasive Open graphtemplate as a PNG with the title changed to Annual Report." - "Render my
Abrasive Open graphtemplate as a PNG withhero.background.colorchanged to#F5F5F5." - "Render my
Abrasive Open graphtemplate as a five-second MP4 with the title changed to Annual Report." - "Permanently update my saved
Abrasive Open graphtemplate to use a white artboard background."
Use the exact template name when possible. You can ask the assistant to list your templates with previews first if you do not remember it.
Troubleshooting
The client reports an authentication error
For OAuth connections, disconnect Robolly in the MCP client and connect it again. If the connection was revoked in Robolly Account settings, a new browser approval is required.
For API-key connections, confirm that the authorization header starts with Bearer followed by your Robolly API key:
Authorization: Bearer YOUR_ROBOLLY_API_KEY
Do not add the user- prefix used by the Robolly dashboard.
Opening the MCP URL in a browser shows an error
This is expected. The MCP endpoint accepts protocol requests from MCP clients and does not provide a normal web page.
The client cannot connect or discover tools
Confirm that the client supports Streamable HTTP. OAuth connections also require support for remote MCP OAuth authorization. Robolly does not currently expose an SSE or local stdio MCP server.
A render does not contain the expected dynamic content
Ask the assistant to use get_template_modifications first. Modification names must match the element names configured in the template.