MCP
Generate straight from the chat you already use.
Paste one URL, or run one command, and Miravely's tools show up right there -- upload a photo, ask for a shot, a clip, or a full tour.
One URL, then sign in once
Add the connector
Settings → Connectors → Add custom connector. Paste this URL and leave everything else as it is.
https://miravely.com/api/mcpSign in once
Claude sends you to Miravely, you click Allow, and it is connected. No key to generate, nothing else to paste.
Start creating
Start a chat and ask it to upload a photo, or generate an establishing shot.
Any other MCP client works the same way -- paste the same URL and sign in if it supports that, or send a personal key as an Authorization header if it does not.
Tools
What shows up in the chat.
upload_photoUploads a photo attached in the chat (JPEG/PNG/WebP, max 3 MB) and returns a photoPath.
get_credit_balanceFree. Returns the account’s current credit balance.
generate_establishingSpends credits. Starts an establishing-shot video from one photo.
generate_card_dropSpends credits. Starts a card-drop video from one photo.
generate_day_to_duskSpends credits. Starts a day-to-dusk clip from one photo.
plan_tour_roomsFree. Labels a set of uploaded photos by room and orders them for a tour.
create_tourSpends credits. Starts every clip of a multi-room walk-through tour at once.
retry_tour_clipSpends credits. Regenerates one clip of an existing tour by index.
check_jobFree. Status of a single-clip job (establishing / day-to-dusk / card drop).
check_tourFree. Status of a multi-clip tour, including each clip.
Every call is logged against the key or connected app that made it, the same as a direct API call -- see it in Settings → Developer.
FAQ
Before you connect anything.
Do I need to install anything?
No. The hosted connector is a URL, not a program. In Claude you paste it into the Connectors panel and approve one sign-in prompt; in Claude Code or Cursor you paste it with a personal key as a header. A separate, locally-run version also exists for anyone who would rather run the server themselves.
What can a connected app do?
Anything your own browser session can: upload photos, start generations, spend credits, read your balance and job history. It cannot change billing, delete your account, or see your password. Treat a personal key like a password -- revoke it from Settings if it leaks.
Does Claude get my Miravely password?
No. Signing in happens on miravely.com, never inside Claude. Claude receives a token scoped to your account that you can take back at any time from Settings -> Developer -> Connected apps, and it expires on its own if it goes unused.
Will it spend my credits without asking?
Every credit-spending tool says so in its own description, and a well-behaved client like Claude will confirm the cost with you first. Miravely itself does not add a second confirmation step on the server -- the key’s whole point is acting on your behalf the way a script would.
Do Claude Code and Cursor sign in the same way?
Not yet -- those two send a personal key instead: claude mcp add --transport http miravely https://miravely.com/api/mcp --header "Authorization: Bearer <your key>" (Claude Code), or the equivalent headers field in Cursor’s mcp.json. The endpoint is the same one either way.
How do I revoke access?
Settings -> Developer. Signed-in apps sit under Connected apps with a Disconnect button; personal keys have a Revoke button next to them. Either one stops working immediately, everywhere it was used.
Does this work with any other MCP client?
Any client that accepts a remote connector URL over Streamable HTTP can use https://miravely.com/api/mcp -- signing in if it supports OAuth, or sending a personal key as an Authorization header if it does not. We have only written exact steps for the three clients above because those are the ones we could verify end to end.