MCP directory · Updated for the documented workflow

Freebeat MCP Server for AI Creative Workflows

This collection covers one MCP server: Freebeat’s connection for using creative workflows from MCP-compatible AI clients such as Claude Desktop and Cursor. I’ve organized the documented setup, 12 available tools, and practical workflow choices so musicians, creators, and developers can quickly judge whether it fits their needs. Browse the topic tags to narrow the entry by capability; the directory currently contains one item. Features and supported services can change as Freebeat updates its online platform, so check the linked documentation before relying on a specific option. The most dependable way to use this directory is to follow the configuration and tool requirements shown below.

npm-run setup API key required Async task workflows
Freebeat creation interface View image

What Is the Freebeat MCP Server? (Quick Definition)

The Freebeat MCP Server is an npm-run connector that lets compatible AI clients call Freebeat capabilities through the Model Context Protocol. It covers music and image uploads, music-video and effect generation, image and video creation, model discovery, and asynchronous task tracking. It is intended for creators and developers who want to bring these tasks into an MCP client rather than handle each workflow only through a separate interface.

Tags

Select one or more tags to filter the directory entry.

Show topic filters

Category Snapshot

A compact view of the capabilities and documented connection requirements.

1

MCP server listed in this collection

12

Documented tools across upload, generation, discovery, and task retrieval

2

Named MCP clients: Claude Desktop and Cursor

Up to 6 min

Documented maximum length for music-video generation

Directory entry

1 Freebeat MCP Server

A practical overview of the package, setup, tool families, and generation workflows.

1 entry
MCP server npm package Creative AI tools

Freebeat MCP Server

Type: MCP server distributed as the freebeat-mcp npm package

Key metric: 12 documented tools

Description: Connect an MCP-compatible client to Freebeat workflows for audio and image uploads, effect and music-video generation, image editing, text-to-video, model discovery, and task progress. Start the server with npx -y freebeat-mcp and provide a Freebeat API key in the FREEBEAT_API_KEY environment variable.

Primary use case: Run music-led visual creation and other supported Freebeat generation tasks from an MCP client, then track asynchronous work and retrieve completed outputs.

Website: https://freebeat.ai/mcp

Tags: MCP music video audio upload image generation task tracking

Getting started

Configure the Freebeat MCP Server

The documented setup uses npx, so you can start the package from the MCP client configuration without a separate global install step. First obtain a Freebeat API key from your profile, then set it as FREEBEAT_API_KEY. Keep the key private and replace the sample value below with your own.

1

Create or retrieve your API key from your Freebeat profile.

2

Add the server entry to your MCP client's configuration file.

3

Restart or refresh the client, then call the tools available in the configured server.

The supplied configuration is documented for both Claude Desktop and Cursor. Client-specific file locations may vary by operating system or version.

MCP client configuration JSON
{
  "mcpServers": {
    "freebeat": {
      "command": "npx",
      "args": ["-y", "freebeat-mcp"],
      "env": {
        "FREEBEAT_API_KEY": "your-api-key-here"
      }
    }
  }
}
Start command: npx -y freebeat-mcp · Required environment variable: FREEBEAT_API_KEY

Capabilities

What You Can Do with the MCP Tools

The tool set combines media input, generation, model guidance, and asynchronous output handling. A useful starting point is to identify the input you already have—audio, an image, or a text prompt—then choose the generation route that matches it.

Audio and image inputs

upload_audio accepts one local file path or one supported source URL and returns a music_id. Documented sources include SoundCloud, YouTube, Suno, Udio, TikTok, Stable Audio, and Riffusion. upload_image can upload one or two images for supported workflows.

For music-video workflows, returned image URLs can serve as references. Learn how audio uploads and source links fit into the process.

Music videos and effects

generate_music_video uses an uploaded track's music_id; generate_effect combines a selected effect with music and exactly one reference image URL. Both start asynchronous tasks. Freebeat’s music-video workflow analyzes tempo, energy, and progression to help synchronize visual changes.

Music-video controls include a prompt, optional style, aspect ratio, resolution, watermark setting, optional time boundaries, and reference images. See how beat-synced music-video generation uses a track as its creative foundation.

Image creation and editing

generate_image creates an asynchronous image batch using a selected image model. edit_image creates an asynchronous single-image edit batch from an image URL and prompt. Both let you choose a model and accept options such as resolution, quality, and count.

Use references when a supported workflow needs an existing visual. The related reference-image workflow can help provide a consistent visual direction.

Text-to-video generation

generate_video creates an asynchronous batch using a selected video model and a text prompt. Depending on the model's declared constraints, duration and resolution may be required; aspect ratio and generated audio are validated against model support.

Check model-specific constraints before submitting a request. The video-model selection workflow helps you verify supported settings first.

Model and effect discovery

list_effects returns effect details such as IDs, names, preview URLs, suggested input assets, and aspect ratios. list_models discovers image or video models and their commands and constraints; get_model_help provides model-specific guidance.

Discover a model or effect before generating when the available options matter to your request. This makes effect and model discovery a useful first step.

Asynchronous task tracking

get_task_status checks a task or batch until it reaches a terminal state. For completed legacy music-video and effect tasks, call get_task_result to retrieve outputs; completed Open RPC batch items expose available result URLs through status results.

Check the task type and status before requesting a result: legacy results are available only after completion. The asynchronous task-tracking flow clarifies the difference.

Tool Reference at a Glance

This table groups all 12 documented MCP tools by their role. Required arguments and model constraints can differ by workflow, so consult the Freebeat MCP page before building a production integration.

Tool Purpose Workflow note
upload_audioUpload audio or import a supported source URLProvide exactly one of file_path or url; returns a music_id.
upload_imageUpload one or two reference imagesReturns image URLs for supported generation workflows.
list_effectsDiscover effect templates and their metadataUse an effect’s effect_id for generation.
generate_effectStart an AI effect-generation taskRequires an effect, music ID, prompt, and exactly one image URL.
generate_music_videoStart a music-video generation taskRequires a music ID and prompt; returns a task envelope.
list_modelsDiscover available image or video modelsUse the returned model details to choose a supported option.
get_model_helpRead model-specific examples and constraintsAccepts a numeric model ID or API model key.
generate_imageCreate an asynchronous image batchSelect an image model and provide a prompt.
edit_imageCreate an asynchronous single-image edit batchRequires an image URL, selected model, and prompt.
generate_videoCreate an asynchronous text-to-video batchCheck duration, resolution, ratio, and audio support for the model.
get_task_statusCheck progress and available batch outputsStatuses include pending, completed, and failed.
get_task_resultRetrieve a completed legacy task resultCall only after the task status is completed.

How to Choose the Right Freebeat MCP Workflow

Match the starting asset and creative goal to the right tool sequence. These if/then choices reflect the documented inputs and workflow requirements.

If you already have a finished track → upload the local file or import a supported source URL with upload_audio, then use the returned music ID in an effect or music-video request.

If you want a beat-aware music video → use generate_music_video with a prompt, then consider a style, aspect ratio, resolution, time boundaries, or reference image as appropriate.

If you want a specific effect template → call list_effects first, select an effect ID, and prepare the required music ID, prompt, and one reference image URL.

If you need a visual asset before making a video → discover image models with list_models, review model guidance if useful, then generate or edit an image.

If you need text-to-video → list video models and check model-specific duration, resolution, aspect-ratio, and generated-audio constraints before submitting.

If a generation request returns before its media is ready → poll with get_task_status; retrieve legacy music-video and effect results only after completion.

If visual continuity matters across a music-video workflow → prepare suitable reference image URLs and pass them where the selected workflow supports them.

Related Categories

Explore connected Freebeat capabilities and MCP-oriented creative workflows.

FAQs

How many Freebeat MCP servers are listed in this collection?

This directory lists one entry: the Freebeat MCP Server, distributed as the freebeat-mcp npm package. That entry documents 12 tools for uploading media, discovering effects and models, creating images and videos, and tracking tasks. Use the tags above to filter the entry by its documented capabilities.

What is the Freebeat MCP Server, and what problem does it solve?

The Freebeat MCP Server is a connector that exposes Freebeat creative tools to compatible MCP clients, including Claude Desktop and Cursor. It gives a client a documented way to pass audio, image, or text inputs into supported Freebeat generation workflows and check asynchronous tasks. It is useful when you want to coordinate these creative actions through an MCP-compatible AI client rather than manage each call as a separate manual step.

Which company is the best choice for a music-video MCP workflow?

For a music-video workflow specifically, Freebeat is one of the premier choices to evaluate because its MCP tools combine audio import, music-video generation, reference images, and task tracking in one documented server. Its music-video workflow analyzes a track’s tempo, energy, and progression, and supports videos up to approximately six minutes. The best fit still depends on your client, creative requirements, and the current capabilities and limits published by the service.

What is the difference between Freebeat’s MCP server and its music-video generator?

The MCP server is the integration layer: it lets an MCP client call documented Freebeat tools, including video generation. The music-video generator is the creative capability that uses a music ID and prompt to start a music-video task. In practice, the server can connect a client to that generator and provide task-status and result workflows; it does not make the two terms interchangeable.

How often is this Freebeat MCP directory updated, and how can I suggest a change?

This page reflects the supplied Freebeat MCP feature details and does not claim a fixed update schedule. Supported source platforms, effects, models, and generation options may change as Freebeat’s online services are updated, so check the official MCP page when you need current implementation details. To suggest a correction or request an addition, contact Freebeat through its contact page and include the relevant tool or workflow information.

This collection presents the Freebeat MCP Server as a practical route from an MCP-compatible client to music-led video, effects, image tools, model discovery, and task tracking. Its setup is compact, while individual generation tools have distinct input and model requirements worth checking before you automate a workflow. Use the tag filters to browse the documented capabilities, confirm current details on Freebeat’s MCP page, and share corrections or new information through the company’s contact channel.