Dailymotion MCP server for your agent

To give Claude, Cursor, ChatGPT or another MCP client Dailymotion data, add Apify's hosted MCP server with the Actors ticked below as tools (one by default); the URL is in every config. Sign in with your Apify account or pass an API token; each call runs the Actor and returns Dailymotion records to the agent.

One click, signs in with Apify on first use:

Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):

npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/dailymotion-video-discovery-by-topic-and-channel" --name dailymotion-video-discovery-by-topic-and-channel

Catalogue Actors
1
In this bundle
1
Official API
Limited
Data checked
2026-11-12

Config for your client

Claude Code configterminal or .mcp.json

claude mcp add --transport http dailymotion-video-discovery-by-topic-and-channel "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/dailymotion-video-discovery-by-topic-and-channel"

  1. Run the command in your project folder. Add --scope user to make it available in every project.
  2. Start Claude Code, type /mcp, pick the server and sign in to Apify in the browser window.
  3. No browser sign-in? Add --header "Authorization: Bearer YOUR_APIFY_TOKEN" to the command instead.

Sign-in: OAuth sign-in on first use, or a token header.

Validated, not executed: 7 of 7 checks pass
  • Uses Apify's hosted MCP endpoint over HTTPS
  • The tools parameter lists exactly the chosen Actors as owner/name
  • JSON configs parse and use the client's top-level key and the same URL
  • Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var
  • CLI commands quote the same URL and use the streamable HTTP transport
  • One-click install links decode back to the same URL and carry no token
  • Only placeholders, no real token

Official API or an Actor?

Dailymotion has an official API with limited access

Dailymotion API v2 requires an access token for every call, obtained with a private API key created in Dailymotion Studio. The documented endpoints cover profiles, videos, playlists and uploads; the v2 reference lists no search endpoint.

No price is published; a private API key from Dailymotion Studio is required.

Published limits cover uploads (standard users and creators up to 15 videos or 10 hours per 24 hours). Read request limits are not published.

Dailymotion API v2 documentation

Public video metadata only; respect Dailymotion's terms and creator rights; not legal advice.

Every Dailymotion Actor in the catalogue

ActorReturnsFieldsStore priceLast update
Dailymotion Video Discovery by Topic & Channel Dailymotion videos with views, likes, velocity, duration, thumbnails, tags, geo-blocking and channel/owner details, plus channel records… Fields include title, ownerUsername, views. 8 $0.99 per 1,000 results 2026-10-18

Store links: dailymotion-video-discovery-by-topic-and-channel

Troubleshooting

Why does the client say Unauthorized or invalid token?

Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.

Source: Apify MCP server README

Why did my agent's tool list change after an update?

Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.

Source: Apify MCP server README

What happens when the agent sends input the Actor rejects?

The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.

Source: Apify MCP server README

Claude Code shows Needs authentication. Why?

The server is added but not signed in. Type /mcp in an interactive session and authenticate, or run claude mcp login with the server name. Headless runs with claude -p cannot complete OAuth, so sign in once interactively or use the --header token variant.

Source: Claude Code MCP documentation

Claude Code warns that a tool result is too large. What can I change?

Claude Code warns above 10,000 tokens of tool output and caps it at 25,000 by default (MAX_MCP_OUTPUT_TOKENS raises it). Ask the agent for fewer results per call, for example a lower result limit for the Actor.

Source: Claude Code MCP documentation

Cursor does not show the server's tools. What should I check?

Open the Output panel and pick MCP Logs to see the connection error. A deeplink install that does nothing usually means an older Cursor build; update it or paste the JSON into mcp.json by hand.

Source: Cursor MCP documentation