YouTube MCP server
Videos and channels on YouTube. Add one address to your AI assistant and it can call the 2 tools below itself, with your FoxAPIs key. They cost the same credits as the REST API, and an answer with no data is not charged.
Server address
https://foxapis.com/mcp/data/youtube
Streamable HTTP, bearer key in the Authorization header. This address carries only the YouTube tools; https://foxapis.com/mcp/data carries all of them, and ?source=youtube,github picks several.
What you can ask
Five prompts to give your assistant once the server is added:
- What is the title of this YouTube video and which channel posted it? https://www.youtube.com/watch?v=jNQXAC9IVRw
- What is the YouTube channel @YouTube about? Give me its description and keywords.
- Which channel uploaded each of these three YouTube links?
- What is the channel id of the YouTube channel I link?
- Is the YouTube channel @YouTube verified?
The tools your assistant gets
| Tool | What it returns | Inputs | Credits a call |
|---|---|---|---|
youtube_video | A YouTube video's title, channel name and thumbnail, from its link (view counts and dates are not returned). | url (required) | 2 |
youtube_channel | A YouTube channel: name, description, keywords, verification flag and channel id, from its link. | url (required) | 2 |
Credits come from the same file as the pricing page. Plans and top-ups are on pricing.
Set it up
Use your FoxAPIs key (it starts with fxp_) as the bearer token. Get one free at foxapis.com/trial.
Claude Code
Run in a terminal. Its docs.
claude mcp add --transport http foxapis-data https://foxapis.com/mcp/data/youtube \ --header "Authorization: Bearer YOUR_KEY"
The Claude Code docs show this form (--transport http, name, URL, --header) for a server that takes a bearer token.
Cursor
.cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project. Its docs.
{
"mcpServers": {
"foxapis-data": {
"url": "https://foxapis.com/mcp/data/youtube",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}Cursor's remote-server example uses a url and a headers object.
VS Code (Copilot)
.mcp.json at the workspace root, or ~/.copilot/mcp-config.json. Its docs.
{
"mcpServers": {
"foxapis-data": {
"type": "http",
"url": "https://foxapis.com/mcp/data/youtube",
"headers": {
"Authorization": "Bearer YOUR_KEY"
},
"tools": [
"*"
]
}
}
}Do not store a real key in a file you share.
Cline
cline_mcp_settings.json (open it from Cline's MCP Servers panel). Its docs.
{
"mcpServers": {
"foxapis-data": {
"type": "streamableHttp",
"url": "https://foxapis.com/mcp/data/youtube",
"headers": {
"Authorization": "Bearer YOUR_KEY"
},
"disabled": false,
"autoApprove": []
}
}
}Cline's docs say that leaving type out selects the older SSE transport, so keep type.
Zed
settings.json (Zed: open settings). Its docs.
{
"context_servers": {
"foxapis-data": {
"url": "https://foxapis.com/mcp/data/youtube",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}
n8n
an MCP Client Tool node in a workflow. Its docs.
Endpoint: https://foxapis.com/mcp/data/youtube Server transport: HTTP Streamable Authentication: Header Auth Name: Authorization Value: Bearer YOUR_KEY
Not run by us: the fields are the ones n8n's MCP Client Tool documents. The server speaks Streamable HTTP.
Claude Desktop and ChatGPT
Not covered here: their custom-connector screens ask for sign-in (OAuth) or no authentication, and this server takes a bearer key in a header, so it works best in the clients above. We have not tested it in either.
A real answer
The youtube_video tool called once through a real MCP client session on 20 November 2026 with the input {"url":"https://www.youtube.com/watch?v=jNQXAC9IVRw"}. Long text is cut and lists are cut to three items for display; it is not invented.
{
"url": "https://www.youtube.com/watch?v=jNQXAC9IVRw",
"platform": "youtube",
"extracted_at": "2026-11-20T11:13:46.669639+00:00",
"title": "Me at the zoo",
"author_name": "jawed",
"author_url": "https://youtube.com/channel/",
"published_at": "Apr 23, 2005",
"date_source": "youtube_dateText",
"thumbnail_url": "https://i.ytimg.com/vi/jNQXAC9IVRw/hqdefault.jpg",
"content_type": "video",
"extras": {
"source": "youtube_oembed",
"note": "Title, channel and thumbnail only: YouTube did not serve the watch page to our network, so views, likes and the publish date are not avai..."
},
"credits_used": 2,
"latency_ms": 694
}
Charged: 2 credits.
Try it free
Runs the youtube_video call with the sample input below. No key and no sign-up; a few runs a day per visitor.
{
"url": "https://www.youtube.com/watch?v=jNQXAC9IVRw"
}
Other data-source MCP servers
Substack · Bluesky · Mastodon · Twitch · SoundCloud · Last.fm · all of them
Free to start: 100 credits, no card. Then from $10. Credits you buy never expire.
Get my free keyThe same data over REST: YouTube video · YouTube channel. More: all MCP servers · people and company tools