mcpField
L
luma-mcp

luma-mcp

Local
github.com/runapi-aiMedia & Design0Updated 1w ago
Repository

About luma-mcp

luma-mcp is a focused RunAPI MCP server for agents that need to inspect existing Luma tasks. The model line is retired, so it supports historical task lookup but not new task submissions.

Key features

  1. 01Fetch task status and latest payload
  2. 02Look up historical Luma tasks
  3. 03Authenticate through login or API key

Use cases

  1. 01Check the status of an existing Luma task
  2. 02Retrieve the latest result payload from a task

MCP support

It exposes `get_task` and `check_pricing` to MCP clients. New task submissions are unavailable because the model line is retired.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "runapi-builder-luma": {
      "command": "npx",
      "args": [
        "-y",
        "@runapi.ai/luma-mcp"
      ],
      "env": {
        "RUNAPI_API_KEY": "<RUNAPI_API_KEY>"
      }
    }
  }
}
Run commandnpx -y @runapi.ai/luma-mcp
Environment variables to set
RUNAPI_API_KEYSecretOptional RunAPI API key for headless hosts. Interactive MCP hosts can use the login tool, which writes shared RunAPI config.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@runapi.ai/luma-mcp0.3.1

Tools

4

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
forcebooleanNoRe-run browser login when the current credential comes from the local config file.

Details

From the project README

RunAPI Luma MCP Server

Luma historical task access for AI agents: query existing tasks through one focused MCP server.

Works with Claude Code, Codex, Cursor, Windsurf, VS Code, Roo Code, and any MCP-compatible host.

npm version GitHub repository Apache-2.0 license MCP Server 0 models

Install | Tools | Models | Agent Prompts | Configuration | Links

Why This Package?

@runapi.ai/luma-mcp is a focused Model Context Protocol server for the Luma model line on RunAPI. It gives MCP-compatible assistants direct access to 0 endpoints and 0 model variants without loading the full RunAPI catalog.

Use this per-model server when an agent should stay scoped to Luma. Use @runapi.ai/mcp when one assistant should discover every RunAPI model line.

luma-modify-video was retired on 2026-10-14T00:00:00Z. New requests return HTTP 410 before task creation or balance deduction. Existing tasks can still be queried. This model ID is not mapped to another model.

Install

Add it to Claude Code:

claude mcp add luma -s user -- npx -y @runapi.ai/luma-mcp

Use project scope when the server should be shared with a repository:

claude mcp add luma -s project -- npx -y @runapi.ai/luma-mcp

Codex, Cursor, Windsurf, VS Code, Roo Code, and other MCP hosts can use the same stdio command:

{
  "mcpServers": {
    "luma": {
      "command": "npx",
      "args": ["-y", "@runapi.ai/luma-mcp"]
    }
  }
}

No models in this package accept new tasks. check_pricing returns no supported model. For historical task lookup, ask your assistant to call the login tool. It opens a browser login and saves credentials to ~/.config/runapi/config.json, the same file used by runapi login. Headless and CI hosts can still set RUNAPI_API_KEY before starting the MCP host.

Ready-made examples are in examples/ for Claude, Cursor, Windsurf, VS Code, and Roo Code.

Tools

ToolAuthPurpose

| get_task | Yes | Fetch the current status and latest payload for an existing task. | | check_pricing | No | Returns no supported model because this model line is retired. |

Models

Luma covers 0 model variants across 0 endpoints. Each tool accepts the models listed for it:

ToolModels

Model availability can change between releases. Use check_pricing or the Luma model page for the current catalog view.

Agent Prompts

Query an existing task with get_task. New requests for this retired model return HTTP 410.

Check the status of my existing Luma task with RunAPI.

The assistant calls get_task with the task id and returns its status and available result.

Configuration

The server resolves auth in this order:

  1. RUNAPI_API_KEY environment variable, useful for headless and CI hosts
  2. ~/.config/runapi/config.json, created by the MCP login tool or runapi login
  3. No key, which still allows check_pricing

The config file is normally managed by login. A pre-provisioned headless config can use:

{
  "apiKey": "your_runapi_key"
}

Do not commit real API keys.

Links

ResourceURL
Luma model pagehttps://runapi.ai/models/luma
npm package@runapi.ai/luma-mcp
GitHub repositoryrunapi-ai/luma-mcp
RunAPI MCP overviewrunapi.ai/mcp
RunAPI docsrunapi.ai/docs

License

Licensed under the Apache License, Version 2.0.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.