Use remote MCP with OAuth to create AI music videos in Codex and other compatible clients, or run the local stdio server with a dedicated API key.
npx -y bizmuse-mcpRecommended · Remote OAuth
Add the Bizmuse AI Music Video Generator MCP endpoint to Codex or another remote MCP client. Sign in in the browser and review the requested scopes; no API key is copied into the client.
https://bizmuse.ai/api/mcpLocal stdio · API key
Use this path for clients that only launch local stdio servers. Keep the dedicated API key in the server environment or credential store.
npx -y bizmuse-mcpUse this local path when your client cannot connect to a remote Streamable HTTP MCP server. The client starts the package when a conversation needs a BizMuse tool.
npx -y bizmuse-mcpStore a BizMuse API key in the server environment so AI music video tasks, references, and finished assets stay connected to your account.
BIZMUSE_API_KEY=your_keyAsk the agent to inspect Bizmuse AI Music Video Generator options or prepare a draft request before submitting a render.
Create a vertical music video for song.mp3The agent passes audio, direction, aspect ratio, and output intent as explicit fields instead of compressing everything into one prompt.
The agent can inspect available Bizmuse AI Music Video Generator models and their input requirements before submitting a task.
Local files and approved media URLs can be attached to the same request while their role remains visible to the agent.
Vertical and landscape targets are selected as generation parameters, keeping platform framing out of prompt guesswork.
Submission returns a task ID that the agent can use to check status, progress, failure details, and final assets.
Completed video and cover assets remain in BizMuse history so a conversation never becomes the only record of a job.
Keep the visual brief beside lyrics, release notes, and campaign planning while BizMuse handles rendering.
Compare directions and references in conversation, then submit only the version that is ready for production.
Let an agent assemble repeatable requests while every generated asset stays tied to the team workspace.
Move an exported track from music ideation into visual production without rebuilding its context in another tool.
MCP lets an agent call defined Bizmuse AI Music Video Generator operations with structured arguments. Use remote OAuth when the client supports Streamable HTTP, or use the local stdio server with an API key when it does not.
Remote access requires an MCP client that supports Streamable HTTP and OAuth. Local access works with desktop clients or coding agents that can launch a stdio MCP server and provide environment variables.
For remote OAuth, sign in to BizMuse when the client opens the authorization flow and review the requested scopes. For local stdio, keep a dedicated API key in the server environment or client credential store, never in prompts or committed configuration.
Yes. It can gather the soundtrack, references, model, format, and creative direction first, then present the prepared request before submission.
Use a readable local file path or a direct media URL. Music-platform page URLs are not audio files, so export the track first.
No. Generation runs as a BizMuse task. The agent can retain the task ID, continue other work, and query progress later.
For remote OAuth, revoke the connected application or its tokens from your account security controls. For local stdio, delete the server entry and revoke its API key in BizMuse. Existing workspace assets remain available to your account.
Connect with remote OAuth, review the requested permissions, and use an eligible Bizmuse account to create music videos in your agent.
See connection optionsRequires an eligible Bizmuse account