MCP library

Your assistant.
Our products.

Bring the tools you use into the conversation. Model Context Protocol (MCP) connects an AI assistant to a product's data and actions. Find a Workflow connection below and follow its setup guide.

Browse connections How to connect

The library

Find your connection.

Each connection has its own account and permissions. Open connection settings for an example configuration. Product guides may ask you to sign in.

Read and write

Voice Buddy

Turn text into speech, transcribe recordings, convert audio and work with voices and clones.

Authentication: Workspace API key; Use your Voice Buddy API key in the Authorization: Bearer header.
MCP endpoint: https://voicebuddy.radioworkflow.com/api/mcp

Connection settings

Example for a remote HTTP client using mcpServers. If your client uses another format, enter the same endpoint and bearer header.

{
    "mcpServers": {
        "voice-buddy": {
            "url": "https://voicebuddy.radioworkflow.com/api/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_API_KEY"
            }
        }
    }
}

Replace the placeholder in your client's credential settings. Keep the key out of shared configuration files.

Setup guide Manage API keys

Read and write

Jingle Buddy

Compose music, create jingles and station imaging, separate stems and check render progress.

Authentication: Workspace API key; Use your Jingle Buddy API key in the Authorization: Bearer header.
MCP endpoint: https://jinglebuddy.radioworkflow.com/api/mcp

Connection settings

Example for a remote HTTP client using mcpServers. If your client uses another format, enter the same endpoint and bearer header.

{
    "mcpServers": {
        "jingle-buddy": {
            "url": "https://jinglebuddy.radioworkflow.com/api/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_API_KEY"
            }
        }
    }
}

Replace the placeholder in your client's credential settings. Keep the key out of shared configuration files.

Setup guide Manage API keys

Read and write

Meet Buddy

Work with your workspace's meetings, contacts and supported communication workflows.

Authentication: API key or OAuth; Use a scoped workspace API key in the Authorization: Bearer header. Registered OAuth clients can also connect on behalf of a member.
MCP endpoint: https://meetbuddy.radioworkflow.com/api/mcp

Connection settings

Example for a remote HTTP client using mcpServers. If your client uses another format, enter the same endpoint and bearer header.

{
    "mcpServers": {
        "meet-buddy": {
            "url": "https://meetbuddy.radioworkflow.com/api/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_API_KEY"
            }
        }
    }
}

Replace the placeholder in your client's credential settings. Keep the key out of shared configuration files.

Setup guide Manage API keys

Permission based

Radio Workflow

Connect an assistant to your station's accounts, logs, proposals and other supported Radio Workflow workflows.

Provided through the API Console.

Authentication: OAuth sign-in; Add the endpoint in your assistant, sign in to Radio Workflow and approve the requested access.
MCP endpoint: https://console.radioworkflow.com/api/mcp

Connection settings

Example for a remote HTTP client using mcpServers. If your client uses another format, enter the same endpoint and connect with OAuth.

{
    "mcpServers": {
        "radio-workflow": {
            "url": "https://console.radioworkflow.com/api/mcp"
        }
    }
}

Setup guide Open API Console

Read only

Signal

Read executive metrics, business overviews and morning briefs for your Radio Workflow workspace.

Authentication: Workspace API key; Use a read-only Signal API key in the Authorization: Bearer header.
MCP endpoint: https://signal.radioworkflow.com/api/mcp

Connection settings

Example for a remote HTTP client using mcpServers. If your client uses another format, enter the same endpoint and bearer header.

{
    "mcpServers": {
        "signal": {
            "url": "https://signal.radioworkflow.com/api/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_API_KEY"
            }
        }
    }
}

Replace the placeholder in your client's credential settings. Keep the key out of shared configuration files.

API reference Manage API keys

Permission based

Affiliate Portal

Read weekly network orders, changes and audio, report affidavits and follow updates. Signing a week stays in the portal.

Authentication: OAuth or station API key; Connect with OAuth as a portal user, or send a scoped station key in the Authorization: Bearer header for automation.
MCP endpoint: https://affiliates.radioworkflow.com/api/mcp

Connection settings

Example for a remote HTTP client using mcpServers. If your client uses another format, enter the same endpoint and bearer header.

{
    "mcpServers": {
        "affiliate-portal": {
            "url": "https://affiliates.radioworkflow.com/api/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_API_KEY"
            }
        }
    }
}

Replace the placeholder in your client's credential settings. Keep the key out of shared configuration files.

Setup guide Manage API and MCP

Release pending

Talent Buddy

Work with assigned jobs and scripts, upload and deliver audio, manage attachments and read earnings with the permissions on your key.

MCP setup is documented, but the integration release is still pending. Confirm availability with the Talent Buddy team before connecting.

Authentication: Scoped API key; Use a Talent Buddy API key in the Authorization: Bearer header. Delivered audio still waits for producer review.
MCP endpoint: https://talent.radioworkflow.com/api/mcp

Connection settings

Example for a remote HTTP client using mcpServers. If your client uses another format, enter the same endpoint and bearer header.

{
    "mcpServers": {
        "talent-buddy": {
            "url": "https://talent.radioworkflow.com/api/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_API_KEY"
            }
        }
    }
}

Replace the placeholder in your client's credential settings. Keep the key out of shared configuration files.

Setup guide Manage API keys

Permission based

Compliance

Work with station matching and scans, political records, issues/programs, EEO and NCE preparation, deadlines and assigned work.

Keys expire and can be revoked. Each call is checked against the current access of the person who created the key.

Authentication: Scoped workspace API key; Use a Compliance API key in the Authorization: Bearer header. The same key and permissions work for REST and MCP.
MCP endpoint: https://compliancebuddy.radioworkflow.com/api/mcp

Connection settings

Example for a remote HTTP client using mcpServers. If your client uses another format, enter the same endpoint and bearer header.

{
    "mcpServers": {
        "compliance-buddy": {
            "url": "https://compliancebuddy.radioworkflow.com/api/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_API_KEY"
            }
        }
    }
}

Replace the placeholder in your client's credential settings. Keep the key out of shared configuration files.

OpenAPI contract Manage connections

Read and write

RevBuddy

Work with promotion kits, campaigns, leads, audience, stations, audio and revenue goals in your station workspace.

Requires an eligible Cluster workspace. Each tool uses the permissions on your key.

Authentication: Scoped workspace API key; Use your RevBuddy API key in the Authorization: Bearer header. An owner creates the key and chooses its permissions.
MCP endpoint: https://revbuddy.radioworkflow.com/api/mcp

Connection settings

Example for a remote HTTP client using mcpServers. If your client uses another format, enter the same endpoint and bearer header.

{
    "mcpServers": {
        "rev-buddy": {
            "url": "https://revbuddy.radioworkflow.com/api/mcp",
            "headers": {
                "Authorization": "Bearer YOUR_API_KEY"
            }
        }
    }
}

Replace the placeholder in your client's credential settings. Keep the key out of shared configuration files.

Setup guide Manage API keys

Other product integrations

Table Buddy

Table Buddy publishes a REST API. Its MCP connection is not available yet; use the API reference for current integration options.

API reference

Getting connected

From endpoint to assistant.

Pick a product.

Open its setup guide. You will need an account with that product and an assistant that supports remote MCP servers over HTTPS.
Add the connection.

Paste the MCP endpoint into your assistant's connector settings. Follow the product guide to sign in with OAuth or supply an API key.
Choose the access.

Grant the permissions your workflow needs. Some connections can change data, contact people or use your product allowance; check the guide before enabling actions.

Need a hand? Contact the product team, or read about building on our products.

Your assistant. Our products.

Find your connection.

Voice Buddy

Jingle Buddy

Meet Buddy

Radio Workflow

Signal

Affiliate Portal

Talent Buddy

Compliance

RevBuddy

Other product integrations

Table Buddy

From endpoint to assistant.

Pick a product.

Add the connection.

Choose the access.

Your assistant.
Our products.