ContentBroadcast MCP

Your AI assistant. Your next audience.

Apply for Bilibili channel management
directly through a compatible AI assistant.

Connect to ContentBroadcast

Public endpoint · verified
https://mcp.contentbroadcast.com/mcp
Transport: Streamable HTTP Agent authentication: No account required

Public integration verified. The public MCP service has completed initialization, tool discovery, and a live application submission. An identical retry returned the same application reference. The service runs independently of your computer.

One tool. Three details.

submit_creator_application
  • 01
    Name name · string · required
  • 02
    Email address email · string · required
  • 03
    YouTube channel URL channel_url · string · required

Submission flow

  1. 1 The user authorizes sending their application details.
  2. 2 The AI client calls the MCP tool with all three fields.
  3. 3 The MCP server submits to the live signup API and returns an application reference.

The backend API credential stays on the MCP server. Agents and applicants do not supply it.

Tool reference

Required input · JSON object

Use this tool to request contact from ContentBroadcast about Bilibili content distribution and channel management.

Field Type Expected value
name string Applicant’s name, 1–200 characters after trimming.
email string Valid contact email address, up to 254 characters.
channel_url string HTTPS YouTube channel URL, up to 2,048 characters. Common forms include /@handle, /channel/ID, /c/name, and /user/name.
Tool arguments · example only
{
  "name": "Alex Morgan",
  "email": "alex@example.com",
  "channel_url": "https://www.youtube.com/@example"
}

Pass this object to submit_creator_application through your MCP client. This is not a raw HTTP request.

Success result · illustrative
{
  "status": "received",
  "application_id": "CB-example-reference",
  "message": "Your application has been received. Our team will contact you by email."
}

The public service returns this JSON as structured content and as text in the MCP result’s content array.

Instructions for agents

  • Collect all three fields. Ask for missing information; do not invent values.
  • Submit only after the user authorizes sending their details to ContentBroadcast.
  • Report receipt only when the tool returns status: received and an application reference.
  • If validation fails, ask the user to correct the affected fields. Authentication or access errors need the server operator’s attention.
  • If a connection times out, the outcome may be uncertain. Retrying the exact same details reuses the current server’s idempotency key within the API’s 30-day retention period.
  • Do not claim that an application guarantees acceptance, creates a channel, signs a contract, or completes onboarding.
Python client example · public service

Requires the MCP Python SDK 2.x. Connect directly to the public service. This example submits to the live signup system when executed; opening this HTML does not submit anything.

import asyncio
from mcp import Client

async def main():
    async with Client("https://mcp.contentbroadcast.com/mcp") as client:
        result = await client.call_tool(
            "submit_creator_application",
            {
                "name": "Alex Morgan",
                "email": "alex@example.com",
                "channel_url": "https://www.youtube.com/@example",
            },
        )
        print(result)

if __name__ == "__main__":
    asyncio.run(main())

Submit only after the applicant authorizes sending these details.

Input schema · documentation

This describes the application fields. Connected clients should discover the runtime tool schema using MCP tools/list.

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200
    },
    "email": {
      "type": "string",
      "format": "email",
      "maxLength": 254
    },
    "channel_url": {
      "type": "string",
      "format": "uri",
      "maxLength": 2048
    }
  },
  "required": [
    "name",
    "email",
    "channel_url"
  ],
  "additionalProperties": false
}
Optional local development

Current local test endpoint: http://127.0.0.1:8001/mcp. Localhost refers to the machine running the Python server.

The supplied Python server is an optional development alternative. The public service runs independently of your computer. Local development requires its own private server-side credential configuration; never put it in a client example.

Page and server responsibilities

This HTML is the information page. It is hosted at https://mcp.contentbroadcast.com/. It contains no API credential and makes no application submissions.

The official MCP SDK server serves /mcp. It handles protocol initialization, tool discovery, and tool calls. A browser visit to that endpoint may show an event stream or protocol response rather than a webpage.

The MCP server calls the authenticated website signup handler. Store its API credential in the server’s deployment secrets. Never embed it in this HTML or in an AI client configuration.

The public service uses stateless Streamable HTTP. The website signup handler stores applications and retains idempotency records for 30 days.