Viddo MCP Documentation

Connect Viddo MCP to Grok

Grok supports custom MCP connectors. Add the Viddo server as a Custom connector, approve it in your browser, and Grok can call Viddo tools in any conversation.

Server URL

https://mcp.viddo.ai/mcp

Add the Viddo Connector

Steps

1. 1Open grok.com/connectors.
2. 2Choose New Connector, then Custom.
3. 3Paste the Viddo server URL into the MCP Server URL field.
4. 4Complete the Viddo OAuth sign-in and Google login in the browser window that opens.
5. 5Start a new conversation and ask Grok to list your models.

Choose Custom rather than a built-in connector or a similar entry from the catalog. Viddo is not a pre-installed service, so the Custom entry is the correct path.

Notes and Troubleshooting

Business and Enterprise accounts

Grok Business and Enterprise accounts may require a team administrator to enable or pre-provision connectors in the admin console. If the New Connector option is missing, that is the account policy.

The interface only asks for an API key or Authorization header

Some configurations expose only a static credential field. Do not paste a personal access token there. Note the client version and the admin policy, and use a client build that supports native OAuth for custom connectors.

Connect Viddo MCP to Claude

Claude connects to Viddo through a custom connector. Add the remote MCP server once, approve it in your browser, and every new conversation can call Viddo tools.

Server URL

https://mcp.viddo.ai/mcp

Add the Viddo Connector

Steps

1. 1Open Claude and go to Customize, then Connectors.
2. 2Choose Add, then Add custom connector.
3. 3Paste the Viddo server URL into the remote MCP URL field.
4. 4Set the authentication to Sign in now or Sign in when needed. Prefer the automatic OAuth option when the interface offers one.
5. 5Click Connect and complete the Viddo sign-in in the browser window that opens.
6. 6Start a new conversation and ask Claude to list your models.

Notes and Troubleshooting

Team and Enterprise accounts

Organization admins usually add custom connectors from Organization settings, under Connectors, then Add, then Custom, then Web. Members may then be limited to connectors the organization has published, and cannot add their own.

Ask your administrator whether external MCP servers and third-party OAuth are permitted, and whether user-supplied accounts require approval.

Claude asks for a client ID or client secret

Do not enter one. Normal users never need to fill those fields. If the interface only offers manual OAuth fields and no automatic registration, record what you see and share it with Viddo support, because that case needs a pre-registered client.

I am asked to sign in again on every conversation

The connector is not storing its refresh token. Check the connector settings and confirm it is using OAuth sign-in rather than a fixed header. Repeated sign-in requests are not expected.

Connect Viddo MCP to Gemini

Gemini can call Viddo tools directly once the Viddo MCP server is added as a custom connector. Once it is connected, you can ask for an AI video, an image, or an audio track in the same conversation where you plan the rest of your work.

Server URL

https://mcp.viddo.ai/mcp

Add the Viddo Connector

Steps

1. 1Open gemini.google.com/customize/connectors and find the section for adding a connector.
2. 2Choose Add, then pick the custom MCP server option.
3. 3Paste the Viddo server URL into the URL field, including the /mcp path.
4. 4Select standard MCP OAuth for authentication. Do not paste a static bearer token.
5. 5Save the connector. Gemini opens your browser so you can sign in with your Viddo account.
6. 6Approve the requested permissions and return to Gemini.

Notes and Troubleshooting

No custom connector option in the interface

This is an account or Workspace policy setting. Check with your administrator. It is not a Viddo configuration problem.

The browser sign-in does not come back to Gemini

The connector registered with a redirect address the authorization server did not accept. Close the stale tab, add the connector again, and complete the sign-in in the fresh window.

Tools list is empty after signing in

The authorization did not complete. Remove the connector, add it again, and approve the permissions in the browser window that opens. Do not substitute a business API URL or a fixed token.

A long job appears to hang

Video generation takes several minutes. Ask Gemini to poll the task instead of resubmitting, so the same job is not billed twice.

Connect Viddo MCP to Cursor

Cursor connects to Viddo over remote MCP with OAuth. Add the server to your MCP configuration, click the login button, and your coding agent can call Viddo tools.

Server URL

https://mcp.viddo.ai/mcp

Add the Viddo Connector

Steps

1. 1Go to Settings, then Customize, then MCPs, then New MCP Server to open the mcp.json configuration file. Use your user configuration at ~/.cursor/mcp.json, or create a project-level .cursor/mcp.json.
2. 2Add the Viddo server entry.
3. 3Save the file and reload the Cursor window.
4. 4Go to Settings, then Customize, then MCPs, and locate the viddo server in the list.
5. 5Click the login button and complete the Viddo sign-in in your browser.
6. 6Send a message asking for the model list to confirm the tools are available.

Configuration

User or project configuration

{
  "mcpServers": {
    "viddo": {
      "url": "https://mcp.viddo.ai/mcp"
    }
  }
}

Notes and Troubleshooting

The tool list is empty

Check the MCP panel first to confirm the server is connected, then check the sign-in. Do not add a static bearer token to the configuration as a workaround, because it expires without any obvious error.

The connection works but a job is not created

Your account may have approved read access only. Complete the additional write permission, then retry the same request with the same clientRequestId.

Tool calls need approval on every run

Cursor asks for confirmation before running MCP tools. This is expected behavior. Approving the Viddo tools once and enabling the trusted-server option removes the repeated prompt, subject to your own security policy.

A long job appears to hang

Video generation takes several minutes. Have the agent poll the task rather than resubmitting, so the same job is not billed twice.

Credits and Cost Control

Every generation draws from the credit balance of the account that authorized the connection. The web app and every MCP client share that same balance.

Estimate before you generate

1. Call viddo_get_account and show the remaining credits.
2. Call viddo_estimate_generation for the model and parameters I described.
3. Show me the estimate and wait for my confirmation before you create anything.

Ask for this behavior explicitly the first time you use a new agent. It is the difference between a predictable credit bill and a surprise one.

If a job fails, the agent reports the failure and the request ID. It does not switch models or resubmit on its own, because a retry with different parameters spends credits again.

Troubleshooting

My client shows the server but no tools appear

The connection reached the server but the authorization did not complete. Disconnect the server, sign in again in the browser, and confirm the permission prompt. Do not paste a bearer token into a header field as a workaround.

The browser sign-in does not come back to my client

The client registered with a redirect address the authorization server did not accept. Close the stale tab, start the connection again from the client, and complete the sign-in in the fresh window. Reusing an old callback link always fails.

My client asks me to log in every time

The client is not storing the refresh token, or it did not request offline_access. Check the client version and its credential storage. Repeated sign-in requests are not normal behavior.

My video link no longer opens

Signed links expire. Query the task again to get a fresh URL. Do not store the old link as a permanent address.

Connecting More Than One Client

Each client registers itself separately and holds its own tokens, so connecting several clients does not multiply your bill. Credits are shared, because every client spends from the same account balance.

To revoke one connection without touching the others, use the disconnect or logout action inside that client. If the client has no revoke action, revoke it from the Viddo account security page and then remove the server entry from the client.

Revoking takes effect immediately. The next tool call from that client fails with an authorization error, and the client has to complete a fresh browser sign-in.

Get Started with Viddo MCP

Connect once and your agent gets the full Viddo catalog, from Kling and Seedance to GPT Image and Flux.

Pick the platform you use from the setup guides above and follow the steps for that client. Every platform uses the same server URL, the same OAuth sign-in, and the same Viddo credits.