Lumiclip vs Runapi AI MCP

A side-by-side look at the Lumiclip and Runapi AI MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Lumiclip logoLumiclipMultimedia Process · Local subprocess (stdio)Turn YouTube videos into short-form clips from any AI assistant49FairAuth: not declaredRunapi AI MCP logoRunapi AI MCPMultimedia Process · Local subprocess (stdio)Unified AI model API for 130+ models across 18 providers. Browse models, check pricing, create image/video/music/audio tasks, poll results, check balance, and call LLM endpoints. Free catalog tools work without an API key. npx @runapi.ai/mcp68GreatAuth: api key required

Verdict: choose Lumiclip for multimedia process work as a local process; choose Runapi AI MCP for multimedia process as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Lumiclip logoChoose Lumiclip when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: LUMICLIP_API_KEY, LUMICLIP_API_URL.
  • You want tools like generate_clips, get_project_status, list_projects.
Explore Lumiclip

Runapi AI MCP logoChoose Runapi AI MCP when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: RUNAPI_API_KEY.
  • You want tools like list_models, get_model_info, list_actions.
Explore Runapi AI MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecLumiclip logoLumiclipRunapi AI MCP logoRunapi AI MCP
CategoryMultimedia ProcessMultimedia Process
Quality signal49/100 · Fair68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsLUMICLIP_API_KEYLUMICLIP_API_URLRUNAPI_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars056
Directory activity 0 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools59

Tools & capabilities

Lumiclip tools 5

  • generate_clipsStart clip generation from a YouTube URL. Returns a `project_id` right away.
  • get_project_statusCheck progress and get clips when ready. Clips are sorted by score (best first).
  • list_projectsList your projects with status and clip counts.
  • get_clipGet full details for a single clip.
  • check_usageSee your plan, remaining credits, and usage.

Runapi AI MCP tools 9

  • list_modelsList RunAPI models from the embedded catalog. Optional filters: modality, service, or action.
  • get_model_infoGet supported endpoint, current runtime pricing, and input constraints for a RunAPI model slug. Add service and action when the model supports multiple endpoints.
  • list_actionsList RunAPI endpoint names grouped by output modality.
  • check_pricingReturn current runtime pricing for a RunAPI model/action pair.
  • search_promptsSearch RunAPI prompt examples by modality, category, tags, text query, model, or featured status. Free, no API key required.
  • check_balanceReturn the authenticated RunAPI account balance and spending metrics.
  • create_taskRun a RunAPI operation with a caller-generated idempotency key. Asynchronous operations can optionally poll until completion.
  • get_taskFetch the current status and latest payload for an existing RunAPI task.
  • loginAuthenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Lumiclip

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "lumiclip": {
      "command": "npx",
      "args": [
        "-y",
        "@lumiclip/mcp-server"
      ],
      "env": {
        "LUMICLIP_API_KEY": "YOUR_LUMICLIP_API_KEY_HERE",
        "LUMICLIP_API_URL": "YOUR_LUMICLIP_API_URL_HERE"
      }
    }
  }
}

Runapi AI MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "runapi-ai-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@runapi.ai/mcp"
      ],
      "env": {
        "RUNAPI_API_KEY": "YOUR_RUNAPI_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Lumiclip is categorized under Multimedia Process and uses a local stdio subprocess. Runapi AI MCP belongs to Multimedia Process and uses a local stdio subprocess. Pick Lumiclip for multimedia process work and Runapi AI MCP for multimedia process.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Lumiclip has no declared pricing — check the project's own site. Runapi AI MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add lumiclip and runapi-ai-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Lumiclip has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Runapi AI MCP has 68/100 (Great) with 7 views, 0 installs and 56 GitHub stars.