YouTube MCP connection
YouTube MCP connection. Follow concrete contracts, examples and reviewable steps using YouTube.
Copy the agent prompt manually
Choose a reachable transport
YouTube MCP connection uses shared discovery and call tools; the platform selects capability IDs and fields rather than a separate gateway.
A client on this computer can test stdio. Localhost inside a container, remote desktop or remote runtime identifies that environment and must be checked separately.
Local configuration example
Replace the placeholder with the absolute project path. This configuration contains no provider key and defaults to demo.
{
"mcpServers": {
"guanliu": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/guanliu/scripts/mcp-server.mjs"
],
"env": {
"GUANLIU_MCP_MODE": "demo",
"GUANLIU_MCP_PORT": "4321"
}
}
}
}First reviewable request
Ask the client to describe youtube.channels.get, inspect its inputs, and explicitly run a fixture. Retain request_id.
{
"capability": "youtube.channels.get",
"params": {
"id": "demo-id"
},
"mode": "demo"
}Connection checks
| Check | Expected result |
|---|---|
| Website reachability | http://127.0.0.1:4321/api/health |
| Discovery | find → describe |
| Transport boundary | Choose explicit data handoff or a local connection based on runtime location |
| Live execution | Disabled; local fixtures or TEST simulation |
| Result recovery | account what=receipt / result |
Clear inputs. Inspectable output.
Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.
Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.
Download contract example (no execution) ↗For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗