General Tools
mixmasterpro.io
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://mixmasterpro.io/mcp
MCP server metadata
- Name
- mixmaster-pro
- Version
- 1.1.0
MixMaster Pro analyzes music mixes for registered users. Prefer protocol 2026-07-28 (stateless). Use mixmaster_account_status before analyze_mix. Pass audio_url or audio_base64 (or upload_id). Poll get_analysis_status. Only a limited teaser is returned — the full analysis stays in MixMaster Pro.
Known tools 3
mixmaster_account_statusCheck whether the authenticated MixMaster Pro user can run a mix analysis.
Inferred read-onlyanalyze_mixAnalyze an audio mix using MixMaster Pro's production mix analysis engine.
Inferred read-onlyget_analysis_statusGet MixMaster Pro analysis job status by analysis_id or job_id.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mixmaster-pro]
url = "https://mixmasterpro.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mixmaster-pro": {
"type": "http",
"url": "https://mixmasterpro.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mixmaster-pro
Remote MCP URL: https://mixmasterpro.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mixmaster-pro": {
"url": "https://mixmasterpro.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mixmaster-pro": {
"type": "http",
"url": "https://mixmasterpro.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mixmaster-pro",
"transport": "streamable-http",
"url": "https://mixmasterpro.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.