LumaMCP

A Model Context Protocol (MCP) server for AI video generation using Luma Dream Machine through the AceDataCloud API.
Generate AI videos directly from Claude, VS Code, or any MCP-compatible client.
Features
- Text to Video - Create AI-generated videos from text prompts
- Image to Video - Animate images with start/end frame control
- Video Extension - Extend existing videos with additional content
- Multiple Aspect Ratios - Support for 16:9, 9:16, 1:1, and more
- Loop Videos - Create seamlessly looping animations
- Clarity Enhancement - Optional video quality enhancement
- Task Tracking - Monitor generation progress and retrieve results
| Tool | Description |
|---|
luma_generate_video | Generate AI video from a text prompt using Luma Dream Machine. |
luma_generate_video_from_image | Generate AI video using reference images as start and/or end frames. |
luma_extend_video | Extend an existing video with additional content. |
luma_extend_video_from_url | Extend an existing video using its URL. |
luma_get_task | Query the status and result of a video generation task. |
luma_get_tasks_batch | Query multiple video generation tasks at once. |
luma_list_aspect_ratios | List all available aspect ratios for Luma video generation. |
luma_list_actions | List all available Luma API actions and corresponding tools. |
Connect: hosted OAuth, API token, or local stdio
The hosted endpoint is https://luma.mcp.acedata.cloud/mcp. Choose one route for the MCP client:
| Route | When to use it | Credential setup |
|---|
| Hosted OAuth | The client supports remote MCP OAuth | Add only the URL, then sign in to AceDataCloud and approve access. No token needs to be pasted into client configuration. |
| Hosted API token | The client cannot finish OAuth, or you need an explicit integration credential | Send an AceDataCloud API token in the Authorization: Bearer β¦ header. Keep it in a local secret store or environment variable. |
| Local stdio | The client runs a local MCP process | Install mcp-luma and pass ACEDATACLOUD_API_TOKEN to that process. It still calls the AceDataCloud API. |
The hosted service advertises OAuth metadata and Dynamic Client Registration (DCR). DCR registers the client application; it is not an API key. OAuth signs you in and the client sends the resulting Bearer token; it may reuse or create an API credential for the account. Browser sign-in still requires an AceDataCloud account. The hosted service can be metered: review current service documentation and displayed pricing before a real operation. Do not configure both an OAuth login and a fixed Authorization header for the same server.
Hosted OAuth examples
- Claude and Claude Desktop chat: Add a remote custom connector in
Customize β Connectors β Add custom connector, enter https://luma.mcp.acedata.cloud/mcp, select sign-in, and choose Register automatically if Claude asks how to register its OAuth client. Complete consent. Claude Desktop's local claude_desktop_config.json is a separate setup. Claude connector guide.
- Claude Code:
claude mcp add --transport http --scope user luma https://luma.mcp.acedata.cloud/mcp, then claude mcp login luma. Check /mcp. Claude Code MCP guide.
- Cursor: Add a remote server with only
https://luma.mcp.acedata.cloud/mcp. For a project, merge the entry below into <project>/.cursor/mcp.json; for personal use, use ~/.cursor/mcp.json. Cursor MCP guide.
- VS Code / Copilot: Run MCP: Add Server, select HTTP, enter
https://luma.mcp.acedata.cloud/mcp, then finish the browser sign-in. New portable workspace configs use <project>/.mcp.json; the VS Code-specific format below uses <project>/.vscode/mcp.json or the user profile. Check MCP: List Servers. VS Code MCP setup.
- Codex:
codex mcp add luma --url https://luma.mcp.acedata.cloud/mcp, then codex mcp login luma. Its user settings are in ~/.codex/config.toml. Official Codex MCP guide.
Cursor project config (OAuth):
{
"mcpServers": {
"luma": {"url": "https://luma.mcp.acedata.cloud/mcp"}
}
}
VS Code-specific workspace config (OAuth):
{
"servers": {
"luma": {"type": "http", "url": "https://luma.mcp.acedata.cloud/mcp"}
}
}
Hosted API token
Sign in at AceDataCloud Platform, open the service page, and obtain an API credential. A fixed Bearer header is useful when your client lacks OAuth; an invalid header does not fall back to OAuth in Claude Code. The header value is sensitive, so keep it out of committed files and screenshots.
For Claude Code, the shell expands the token when you add the server; treat the saved user MCP config as a secret:
export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'
claude mcp add --transport http --scope user luma https://luma.mcp.acedata.cloud/mcp \
--header "Authorization: Bearer $ACEDATACLOUD_API_TOKEN"
For a Claude Code project config, put a variable reference in <project>/.mcp.json and set that variable in the environment that launches Claude Code:
{
"mcpServers": {
"luma": {
"type": "http",
"url": "https://luma.mcp.acedata.cloud/mcp",
"headers": {"Authorization": "Bearer ${ACEDATACLOUD_API_TOKEN}"}
}
}
}
Cursor uses a different environment-variable syntax in ~/.cursor/mcp.json or an uncommitted project config:
{
"mcpServers": {
"luma": {
"url": "https://luma.mcp.acedata.cloud/mcp",
"headers": {"Authorization": "Bearer ${env:ACEDATACLOUD_API_TOKEN}"}
}
}
}
In VS Code, run MCP: Open User Configuration and merge this server plus its masked input; ${input:...} is for VS Code's user/workspace format and is not portable to the Agent Host .mcp.json format:
{
"inputs": [
{"id": "acedata-luma-token", "type": "promptString", "description": "AceDataCloud API token", "password": true}
],
"servers": {
"luma": {
"type": "http",
"url": "https://luma.mcp.acedata.cloud/mcp",
"headers": {"Authorization": "Bearer ${input:acedata-luma-token}"}
}
}
}
For Cline, use its MCP configuration UI or CLI file ~/.cline/data/settings/cline_mcp_settings.json; its remote transport value is streamableHttp. For JetBrains AI Assistant, add a remote URL from Settings β Tools β AI Assistant β Model Context Protocol (MCP). For Zed, use a context_servers entry with the URL only for OAuth or add a local Bearer header. These clients have different configuration schemas; follow their current UI rather than copying another client's JSON. Cline Β· JetBrains Β· Zed.
Local stdio
Install the package and give the local process an API token:
python -m pip install mcp-luma
export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'
mcp-luma
For Claude Desktop local MCP, merge this entry into the file opened by its developer settings (~/Library/Application Support/Claude/claude_desktop_config.json on macOS). uvx requires uv on PATH:
{
"mcpServers": {
"luma": {
"command": "uvx",
"args": ["mcp-luma"],
"env": {"ACEDATACLOUD_API_TOKEN": "YOUR_API_TOKEN"}
}
}
}
Keep this user-level file private. Self-hosted HTTP uses mcp-luma --transport http --port 8000; expose it only with suitable network and TLS controls. Local execution still calls the AceDataCloud API.
Check before using the service
https://luma.mcp.acedata.cloud/health returning {"status":"ok"} checks endpoint reachability only.
- Confirm that the MCP client loads tools.
luma_list_actions is a reference tool; it does not verify downstream API access or balance.
- If you need a full API check, call
luma_generate_video with your own valid input after reviewing current service documentation and displayed pricing. If the result contains a task ID, call luma_get_task on that same ID until terminal success or failure. Do not resubmit the operation just to check progress.
For 401, check which auth route the client used and whether the token or OAuth session is valid. A 403 may mean an account permission or content moderation failure; read the returned error. Insufficient balance and downstream service failures need their own diagnosis. A listed tool or submitted task does not prove a successful result.
Video Generation
| Tool | Description |
|---|
luma_generate_video | Generate video from a text prompt |
luma_generate_video_from_image | Generate video using reference images |
luma_extend_video | Extend an existing video by ID |
luma_extend_video_from_url | Extend an existing video by URL |
Tasks
| Tool | Description |
|---|
luma_get_task | Query a single task status |
luma_get_tasks_batch | Query multiple tasks at once |
| Tool | Description |
|---|
luma_list_aspect_ratios | List available aspect ratios |
luma_list_actions | List available API actions |
Usage Examples
Generate Video from Prompt
User: Create a video of waves on a beach
Claude: I'll generate a beach wave video for you.
[Calls luma_generate_video with prompt="Ocean waves gently crashing on sandy beach, sunset"]
Animate an Image
User: Animate this image: https://example.com/image.jpg
Claude: I'll create a video from your image.
[Calls luma_generate_video_from_image with start_image_url and appropriate prompt]
Extend a Video
User: Continue this video with more action
Claude: I'll extend the video with additional content.
[Calls luma_extend_video with video_id and new prompt]
Available Aspect Ratios
| Aspect Ratio | Description | Use Case |
|---|
16:9 | Landscape (default) | YouTube, TV, presentations |
9:16 | Portrait | TikTok, Instagram Reels |
1:1 | Square | Instagram posts |
4:3 | Traditional | Classic video format |
3:4 | Portrait traditional | Portrait content |
21:9 | Ultrawide | Cinematic content |
9:21 | Tall ultrawide | Special vertical displays |
Configuration
Environment Variables
| Variable | Description | Default |
|---|
ACEDATACLOUD_API_TOKEN | API token from AceDataCloud | Required |
ACEDATACLOUD_API_BASE_URL | API base URL | https://api.acedata.cloud |
ACEDATACLOUD_OAUTH_CLIENT_ID | OAuth client ID (hosted mode) | β |
ACEDATACLOUD_PLATFORM_BASE_URL | Platform base URL | https://platform.acedata.cloud |
LUMA_DEFAULT_ASPECT_RATIO | Default aspect ratio | 16:9 |
LUMA_REQUEST_TIMEOUT | Request timeout in seconds | 1800 |
LOG_LEVEL | Logging level | INFO |
Command Line Options
mcp-luma --help
Options:
--version Show version
--transport Transport mode: stdio (default) or http
--port Port for HTTP transport (default: 8000)
Development
Setup Development Environment
git clone https://github.com/AceDataCloud/LumaMCP.git
cd LumaMCP
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev,test]"
Run Tests
pytest
pytest --cov=core --cov=tools
pytest tests/test_integration.py -m integration
Code Quality
ruff format .
ruff check .
mypy core tools
Build & Publish
pip install -e ".[release]"
python -m build
twine upload dist/*
Project Structure
LumaMCP/
βββ core/ # Core modules
β βββ __init__.py
β βββ client.py # HTTP client for Luma API
β βββ config.py # Configuration management
β βββ exceptions.py # Custom exceptions
β βββ server.py # MCP server initialization
β βββ types.py # Type definitions
β βββ utils.py # Utility functions
βββ tools/ # MCP tool definitions
β βββ __init__.py
β βββ video_tools.py # Video generation tools
β βββ task_tools.py # Task query tools
β βββ info_tools.py # Information tools
βββ prompts/ # MCP prompts
β βββ __init__.py # Prompt templates
βββ tests/ # Test suite
β βββ conftest.py
β βββ test_client.py
β βββ test_config.py
β βββ test_integration.py
β βββ test_utils.py
βββ deploy/ # Deployment configs
β βββ production/
β βββ deployment.yaml
β βββ ingress.yaml
β βββ service.yaml
βββ .env.example # Environment template
βββ .gitignore
βββ CHANGELOG.md
βββ Dockerfile # Docker image for HTTP mode
βββ docker-compose.yaml # Docker Compose config
βββ LICENSE
βββ main.py # Entry point
βββ pyproject.toml # Project configuration
βββ README.md
API Reference
This server wraps the AceDataCloud Luma API:
Contributing
Contributions are welcome! Please:
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing)
- Commit your changes (
git commit -m 'Add amazing feature')
- Push to the branch (
git push origin feature/amazing)
- Open a Pull Request
Documentation
Documentation
License
MIT License - see LICENSE for details.
Links
Made with love by AceDataCloud