acedatacloud-maestroCAUTION
MCP server for end-to-end AI video production with Maestro through Ace Data Cloud.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Produce complete videos from a natural-language brief with Maestro through the Ace Data Cloud API. Maestro plans the script, creates or sources media, generates voiceover and music, edits, captions, renders, and returns finished video variants.
Connect: hosted OAuth, API token, or local stdio
The hosted endpoint is https://maestro.mcp.acedata.cloud/mcp. Choose one route for the MCP client:
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 connec
d5733301e67cOBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add mcp-maestro --env ACEDATACLOUD_API_TOKEN=${ACEDATACLOUD_API_TOKEN} -- uvx mcp-maestro==0.1.0Trust audit
CAUTIONgrade B · trust 85/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (10 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (9)
logger.info(f"Revoked token: {token.token[:8]}...")callback_url = f"{settings.server_url}/oauth/callback""redirect_uri": callback_url,
callback_url = f"{settings.server_url}/oauth/callback""redirect_uri": callback_url,
callback_url: Annotated[
.ruff.toml
self._cipher = Fernet(base64.urlsafe_b64encode(bytes.fromhex(key)))
Gates applied: no_behavioural_pass.
d5733301e67cfull audit observations/trust-audit/mcp-server/acedatacloud__maestromcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | d5733301e67c | CAUTION | B | 85 | first audit |
Questions
What is the acedatacloud-maestro MCP server?
MCP server for end-to-end AI video production with Maestro through Ace Data Cloud.
Is acedatacloud-maestro safe to connect to an agent?
With care. The audit graded it B (85/100) and found 9 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does acedatacloud-maestro need?
It reads ACEDATACLOUD_API_TOKEN, ACEDATACLOUD_AUTH_BASE_URL, ACEDATACLOUD_OAUTH_CLIENT_ID, MCP_OAUTH_REDIS_PASSWORD, MCP_OAUTH_REDIS_URL and MCP_OAUTH_STATE_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does acedatacloud-maestro run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on PyPI as mcp-maestro.
How current is this page?
The grade is for one exact copy of the source (d5733301e67c), read on 2026-10-10. The repository is watched and re-audited when it changes.