Reelo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REELO_API_KEY | Yes | Your Reelo API key (rk_live_…), obtained under Account › API & MCP at https://www.getreelo.com. Required. | |
| REELO_API_URL | No | Optional API base URL override (defaults to Reelo's public v1 URL). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_boardsA | List boards in your Reelo workspace. Spends no credits. |
| create_boardB | Create an empty board. Spends no credits. |
| get_boardA | Get one board and its pieces. Spends no credits. |
| quote_videoA | Quote a video in whole credits. Spends no credits. Returns quote_id, total_credits, clips and your balance. Always show the price to the user before run_quote. |
| run_quoteA | Run a quote. SPENDS REELO CREDITS (held at start, refunded if the run fails). Requires explicit user confirmation and max_credits >= the quote. |
| get_runB | Run status, charge and outputs. Spends no credits. |
| get_run_assetsB | Temporary download links for a run's outputs. Spends no credits. |
| recreate_from_linkB | Get a scene structure to recreate a video from a link at 15 or 30 s. Nothing is downloaded. Spends no credits. |
| plan_editA | Plan an Edit node (join, trim, text, captions, duck music under voice, effects…). Spends no credits. Send output_seconds (and ratios) to get render_quote: the render price in whole credits; show it to the user before they approve the render in the app. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource or step in the video workflow. quote_video vs. run_quote and get_run vs. get_run_assets are clearly differentiated by their descriptions, so an agent can select correctly.
All tools use consistent snake_case with verb-first names such as list_boards, create_board, get_board, and run_quote. Minor variations like recreate_from_link and plan_edit still fit the same predictable pattern.
Nine tools is well-scoped for this video generation and board management server. Each tool covers a meaningful operation without excessive surface area.
Board coverage is notably incomplete: list, create, and get exist, but there is no update/delete board or add/remove piece operation, leaving create_board as a potential dead end. Run and quote workflows are better covered, but the board lifecycle has significant gaps.