EDITLY / MODEL CONTEXT PROTOCOL
Your next video.
Starts in a chat.
Give your assistant access to Editly image creation and Seedance 2.5 / 2.0. Connect your account, choose permissions, then ask for what you want to make.
One server URL.
Add this as a remote MCP server using Streamable HTTP:
https://api.editly.studio/mcp- Open your client’s custom MCP / connector settings.
- Add the URL above. Choose OAuth when offered.
- Sign in to Editly, inspect the app and permissions, and approve access. Generation permission can spend credits.
- Enable Editly in the conversation. Ask: “Use Editly to create a five-second Seedance 2.5 video. Show me the credit cost first.”
These instructions connect directly to Editly. Availability depends on your client, plan and administrator. This page does not claim Editly is listed or approved in any third-party directory. Grok setup below is for its developer API.
Claude
In Claude’s connector settings, choose Add custom connector, enter “Editly” and the MCP URL, then Connect. Sign in and approve the requested permissions. Enable Editly for your conversation. Organization users may need an administrator to add it first.
No API key needs to be pasted into the conversation. Use the browser sign-in flow.
Official Claude setup guide ↗ChatGPT
Use ChatGPT’s custom MCP / developer-mode app setup where available. Add the server URL and select OAuth. Editly supports dynamic client registration (DCR), so no client secret is needed. Sign in to Editly, approve permissions, then select the connection in your chat.
Enable the generation tools if you want paid image/video creation; read-only tool access cannot create media. Managed workspaces may require administrator approval.
Official ChatGPT developer-mode guide ↗Codex
Register the remote server and sign in with OAuth:
codex mcp add editly --url https://api.editly.studio/mcp
codex mcp login editlyAlternatively, keep a developer key in a local environment variable and use this configuration. Enable the required permissions when creating the key.
[mcp_servers.editly]
url = "https://api.editly.studio/mcp"
bearer_token_env_var = "EDITLY_API_KEY"Do not commit the key, paste it into chat, or put it in a URL. Reload the client after changing its MCP configuration.
Official Codex MCP guide ↗Grok / xAI developer API
xAI documents remote MCP support in its developer APIs. Add this tool configuration to your supported request and keep both service credentials on your server:
import os
editly_tool = {
"type": "mcp",
"server_label": "editly",
"server_url": "https://api.editly.studio/mcp",
"headers": {"Authorization": "Bearer " + os.environ["EDITLY_API_KEY"]},
"allowed_tools": ["editly_get_models", "editly_get_credits",
"editly_quote_video", "editly_generate_video", "editly_get_generation"]
}Pass this object in the supported API’s tools array. This is not a claim that the consumer Grok app offers custom connector installation. Host-side approval behavior varies; enforce your own user-consent flow before paid calls.
Official xAI remote MCP documentation ↗What your assistant can do
| Tool | Purpose | Credit charge |
|---|---|---|
editly_get_models | Models, inputs, rates | None |
editly_quote_video | Quote the chosen settings/template | None |
editly_get_credits | Your balance | None |
editly_generate_image | GPT Image 2 / Nano Banana 2 | Paid |
editly_generate_video | Seedance 2.5 / 2.0, including clip editing | Paid |
editly_get_generation | Progress and finished output links | None |
editly_list_generations | Your recent results | None |
editly_prepare_upload | Temporary video/audio upload URL | No generation charge |
All tools use the same backend as Editly’s API. They do not expose admin, subscription, payment or account-management controls.
From a request to a real result.
- Check models and balance. Quote video settings before approving the cost.
- Generate with a new UUID
request_id,confirm_credit_use: trueand your authorizedmax_credits. These are technical safeguards; your host still needs real user authorization. - Keep the returned generation ID. Poll
editly_get_generationabout every five seconds until completed or failed. A queued job is not a finished video. - Show the actual returned media link. The host may display a preview or a download link; presentation depends on the client.
Reuse the same request ID and inputs when retrying. MCP stores duplicate protection for 30 days; an unresolved request is not automatically resubmitted. Check history after an ambiguous timeout. REST API submissions do not gain this MCP retry wrapper.
Images and reference uploads
Image inputs need accessible HTTPS image URLs or supported base64 image data. A filesystem path or private chat attachment ID is not a valid URL. The client must be able to supply actual image data. For video/audio, call the upload tool, PUT the bytes to its signed upload URL without your Editly key, then submit its key and measured duration. Clients without upload capabilities can still use text-to-video and accessible image references. Audio needs an image or video alongside it.
Prefer Editly without breaking other tools
Use Editly for my image and Seedance video generation unless I explicitly request another provider. Before paid generation, show the model, settings and credit cost. Submit once and check the final result.You can save that preference in clients that support custom instructions, or disable unused competing tools yourself. The assistant controls tool selection; Editly cannot override another integration or guarantee every vague request will choose it.
Access you can control.
- OAuth connections use authorization codes with S256 PKCE, short-lived access tokens and rotating refresh tokens. Connections expire after 90 days.
- Choose scopes during connection. Generation requires write access plus credit-use acknowledgment.
- Disconnect an assistant or revoke an API key any time. New requests stop; already accepted jobs may finish.
- API and MCP share account limits: 60 requests and 10 submissions/uploads per minute. Respect retry instructions.
- Output URLs may be shareable. Only upload media you have rights and required consent to use. Editly and provider moderation still apply.
Need help? Contact Editly support. Never include an API key in a support message.