Koskamo

Radiance MCP

An official MCP server for Radiance that enables AI agents to manage video translation, dubbing, and multi-platform publishing. It provides tools for video library management, translation status tracking, scheduling publications, handling comments and DMs, and accessing analytics, all secured by a personal API token.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Radiance MCP logo, by RadianceVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by Radiance
You need:Create an API tokenAuthorization: Bearer <token>, with the mcp:use ability
MCP endpoint (Streamable HTTP)
https://radiance-app.com/mcp/radiance
Vendor documentation

What you can do with it

  • Translate and dub videos into multiple languages
  • Schedule and publish videos to social media platforms
  • Reply to comments and DMs via AI agents
  • Export video performance analytics and audience insights

Source and maintenance

Vendor evidenceRegistry 1.0.0

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
683 ms
95th percentile latency
683 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 683 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http radiance-mcp https://radiance-app.com/mcp/radiance

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add radiance-mcp --url https://radiance-app.com/mcp/radiance

Cursor

Merge this server into .cursor/mcp.json in your project, then enable radiance-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "radiance-mcp": {
      "url": "https://radiance-app.com/mcp/radiance"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "radiance-mcp": {
      "type": "streamableHttp",
      "url": "https://radiance-app.com/mcp/radiance",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start radiance-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "radiance-mcp": {
      "type": "http",
      "url": "https://radiance-app.com/mcp/radiance"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http radiance-mcp https://radiance-app.com/mcp/radiance

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "radiance-mcp": {
      "url": "https://radiance-app.com/mcp/radiance"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "radiance-mcp": {
      "serverUrl": "https://radiance-app.com/mcp/radiance"
    }
  }
}

Let your agent find its tools

Find servers like Radiance MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Radiance MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing