> For the complete documentation index, see [llms.txt](https://docs.rad.live/rad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rad.live/rad/rad-tv-developer-api/mcp.md).

# MCP

The Rad TV API exposes a **Model Context Protocol (MCP)** server so IDEs and coding agents (e.g. Cursor, Claude) can interact with the API using tools with typed inputs.

## Endpoint

* **URL:** `POST /mcp` (and `GET /mcp`, `DELETE /mcp` for Streamable HTTP)
* **Auth:** Required. Send `Authorization: Bearer <api-key>`. Use an API key from `POST /internal/v0/generate-api-key` (see [API keys](/rad/rad-tv-developer-api/api-keys.md)).
* Production: `https://api.rad.live/mcp`.

{% hint style="info" %}
Protocol version header: `MCP-Protocol-Version: 2025-11-25`.
{% endhint %}

## What MCP provides

* **23 tools** — Map to core API actions: identity, channels, categories, ratings, genres, content, playlists, ingestion, engagement, YouTube. Each tool has a description and an input schema.
* **1 resource** — `rad://api/capabilities` returns JSON with `name`, `version`, `tools` (list of names), `llms_txt`, `graphql`, and `description`.
* **2 prompts** — `create_content_and_upload` (guide for content + TUS upload), `follow_a_channel` (guide to follow by DID).

## Protocol

{% stepper %}
{% step %}

### Initialize

Send an `initialize` JSON-RPC request first (required).
{% endstep %}

{% step %}

### List tools

Use `tools/list` to get all tools and their schemas.
{% endstep %}

{% step %}

### Call tools

Use `tools/call` with `name` and `arguments`.
{% endstep %}

{% step %}

### Resources

Read `rad://api/capabilities` for a summary of capabilities.
{% endstep %}
{% endstepper %}

## When to use MCP vs GraphQL

| Use MCP when                                     | Use GraphQL when                                    |
| ------------------------------------------------ | --------------------------------------------------- |
| Building IDE/agent integrations (Cursor, Claude) | Building web or mobile apps                         |
| You want one action = one tool call              | You need full schema, introspection, custom queries |
| You prefer typed tool arguments                  | You prefer a single endpoint and flexible queries   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rad.live/rad/rad-tv-developer-api/mcp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.