OrynosMusic / Model Context Protocol
Your agent.
Your mastering tools.
Connect your AI client to OrynosMusic. Explore models, check your credits and work with audio through your own account.
Get your API keyOne connection.
Remote HTTP · Bearer authenticationhttps://orynosmusic.com/api/mcpUse your personal OrynosMusic API key. The key belongs in the Authorization header, never in the server URL.
Set up your client.
- Create a personal key.
Sign in with a verified account and open Settings → API keys. Copy the key when it is shown.
- Choose your client.
Some clients read
ORYNOS_API_KEY; others prompt for the key or store a private header. Follow the matching recipe. - Check the connection.
Review the available tools and their permissions, then ask for your credit balance before starting work.
Environment setup examples
Replace YOUR_ORYNOS_API_KEY on your own computer. These commands set the variable for the current terminal only; launch your client from that terminal.
Windows PowerShell
$env:ORYNOS_API_KEY = 'YOUR_ORYNOS_API_KEY'macOS / Linux shell
export ORYNOS_API_KEY='YOUR_ORYNOS_API_KEY'An app opened from a desktop shortcut may not inherit your terminal environment. Set a user environment variable or launch the app from the configured terminal. Keep keys out of shared projects, screenshots and chat messages.
Claude CodeNative remote HTTP connection
Run this in PowerShell or a macOS/Linux shell after setting the environment variable.
claude mcp add --transport http --scope user orynos https://orynosmusic.com/api/mcp --header 'Authorization: Bearer ${ORYNOS_API_KEY}'Keep the single quotes so Claude Code receives the environment-variable reference. Open /mcp in Claude Code to check the connection. Requires Claude Code to be installed.
CodexApp, editor extension and CLI configuration
With Codex CLI installed, run this after setting ORYNOS_API_KEY.
codex mcp add orynos --url https://orynosmusic.com/api/mcp --bearer-token-env-var ORYNOS_API_KEYOr merge this entry into your existing ~/.codex/config.toml.
[mcp_servers.orynos]
url = "https://orynosmusic.com/api/mcp"
bearer_token_env_var = "ORYNOS_API_KEY"Codex adds the Bearer prefix. Restart the client after changing its environment, then check its MCP server list. Do not overwrite your other configuration entries.
Codex MCP referenceCursorNative remote HTTP configuration
Merge this into ~/.cursor/mcp.json for your user account, keeping any existing servers.
{
"mcpServers": {
"orynos": {
"url": "https://orynosmusic.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:ORYNOS_API_KEY}"
}
}
}
}Cursor must inherit ORYNOS_API_KEY. Restart it after an environment change and check the server under Customize → MCP. Remote servers do not read an envFile entry.
Gemini CLIRemote HTTP with a private header
Merge this into your personal ~/.gemini/settings.json. Replace the placeholder locally; this client configuration contains the key.
{
"mcpServers": {
"orynos": {
"httpUrl": "https://orynosmusic.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_ORYNOS_API_KEY"
},
"trust": false
}
}
}Use httpUrl for HTTP, rather than the legacy SSE url field. Restart Gemini CLI and run gemini mcp list. Keep this populated settings file private; no header-variable expansion is assumed here.
VS CodeLocal harness with a secure key prompt
For VS Code's Local harness, open the user-profile MCP file or .vscode/mcp.json. Merge this configuration; VS Code prompts for your personal key.
{
"inputs": [
{
"type": "promptString",
"id": "orynos-key",
"description": "OrynosMusic personal API key",
"password": true
}
],
"servers": {
"orynos": {
"type": "http",
"url": "https://orynosmusic.com/api/mcp",
"headers": {
"Authorization": "Bearer ${input:orynos-key}"
}
}
}
}Use MCP: Add Server to choose the correct destination. Input-prompt servers are not forwarded to Copilot harness sessions; those use the separate configuration below.
Copilot harnessSeparate from VS Code's Local harness
For the Copilot harness, merge this into personal ~/.copilot/mcp-config.json, or the matching COPILOT_HOME location. The process must inherit ORYNOS_API_KEY.
{
"mcpServers": {
"orynos": {
"type": "http",
"url": "https://orynosmusic.com/api/mcp",
"headers": {
"Authorization": "Bearer ${ORYNOS_API_KEY}"
},
"tools": ["*"]
}
}
}This runtime uses ${ORYNOS_API_KEY}, rather than VS Code's ${input:...} syntax. Check your installed harness version and its tool approvals; configuration formats are not interchangeable.
ClineStreamable HTTP with explicit approval settings
In the extension, open MCP Servers → Configure → Configure MCP Servers. Merge this entry and replace the key placeholder locally.
{
"mcpServers": {
"orynos": {
"type": "streamableHttp",
"url": "https://orynosmusic.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_ORYNOS_API_KEY"
},
"disabled": false,
"autoApprove": []
}
}
}The streamableHttp value is case-sensitive. An omitted type can select legacy SSE. Keep the populated file private; this recipe leaves automatic tool approval off.
ZedRemote server for Zed Agent
Use Settings → AI → MCP Servers → Add Server → Add Remote Server, or merge this into the file opened by zed: open settings file.
{
"context_servers": {
"orynos": {
"url": "https://orynosmusic.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_ORYNOS_API_KEY"
}
}
}
}Replace the placeholder only in your private configuration. This connects Zed Agent; terminal threads or external agents can have their own configuration. An absent header can trigger OAuth, which this endpoint does not offer.
Zed MCP referenceLM StudioUse a model that supports tool calls
Open the right sidebar's Program tab → Install → Edit mcp.json. Merge this server and replace the placeholder with your personal key.
{
"mcpServers": {
"orynos": {
"url": "https://orynosmusic.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_ORYNOS_API_KEY"
}
}
}
}Keep the populated file private. This example uses the documented fixed header; it does not assume Cursor's environment interpolation also works in LM Studio. The selected model must support MCP tool use.
LM Studio MCP referenceWindsurf / CascadeVersion-specific legacy Cascade setup
Open Cascade's Actions menu → Open MCP config file. Current Windsurf documentation redirects to Devin Desktop and labels this setup for legacy Cascade, rather than the default Devin Local agent.
{
"mcpServers": {
"orynos": {
"serverUrl": "https://orynosmusic.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:ORYNOS_API_KEY}"
}
}
}
}The process must inherit ORYNOS_API_KEY. Use the configuration action exposed by your installed version. Devin Local uses separate configuration, and Cascade has a combined tool limit.
Start with a question
Let your agent get oriented.
Show the available OrynosMusic mastering models and my credit balance. Explain the options, and ask me before starting a render that uses credits.
Before you render.
Your account, your credits.
Model access, restrictions and render costs come from your OrynosMusic account. A render must explicitly confirm its credit charge. Read-only model and balance requests do not start a render.
Upload once, then use the handle.
The remote server cannot read files on your computer. A client with file-upload support can upload to POST /api/analyze, then pass the returned upload_id to MCP. See the API guide for upload details.
Download when it is ready.
Finished masters remain available for five minutes after rendering completes. Queue and processing time are separate. Ask your client to check the job and save the result promptly.
Choose a client you trust.
Your connected client can act with your key's account access. Review its permissions, and rotate or revoke the key in Settings when needed. This page never asks you to paste a key.
Connector availability.
Claude Desktop, Claude web and Cowork
Custom web connectors can use fixed request headers where Claude exposes that beta feature. Add this server URL, choose No sign in for the OAuth setting, and add an Authorization request header with Bearer YOUR_ORYNOS_API_KEY. The header still authenticates every request to OrynosMusic.
If Request headers is unavailable for your account or organization, this direct setup is unavailable; use Claude Code instead. A shared organization key gives everyone using it the same OrynosMusic account access and credit balance.
Check Claude's current connector requirementsChatGPT custom connectors
This endpoint uses a personal Bearer key. ChatGPT's documented custom-connector setup supports OAuth or no authentication, rather than this fixed-header setup. Direct ChatGPT connector login is not offered here. Codex is a separate client and supports the configuration above.
ChatGPT custom MCP requirementsMCP connects a client to tools, rather than installing an AI model. Available provider models depend on the client. Interfaces and organization policies can change; these documented recipes are not a claim that every installed version or model has been tested.