MCP
Stophy MCP Server
Connect Stophy to Claude, Cursor, Windsurf, and any MCP client. Search YouTube, read transcripts, and inspect channels as agent tools.
The Stophy MCP server exposes YouTube search, video details, transcripts, comments, channels, playlists, suggestions, and credits as tools your agent can call directly. Same data as the REST API. Same credit metering. Same JSON shapes.
Connect over hosted Streamable HTTP at api.stophy.dev/v1/mcp, or run npx @stophy/mcp locally with your API key. Works in Claude Desktop, Claude Code, Cursor, VS Code, and Windsurf.
Connect
Pick hosted HTTP or a local npm server. Both expose the same MCP tools.
Connect to Stophy's hosted Streamable HTTP MCP endpoint. No local process required.
1claude mcp add --transport http stophy https://api.stophy.dev/v1/mcp \2 --header "Authorization: Bearer $STOPHY_API_KEY"Endpoint: https://api.stophy.dev/v1/mcp with Authorization: Bearer st_xxx
Full setup for Claude Desktop, Claude Code, Cursor, VS Code, and Windsurf in the MCP docs.
Setup and tools
Add Stophy to your MCP client, then call YouTube tools from inside the agent session.
1claude mcp add --transport http stophy https://api.stophy.dev/v1/mcp \2 --header "Authorization: Bearer $STOPHY_API_KEY"1{2 "tools": [3 "stophy_search_videos",4 "stophy_get_video",5 "stophy_get_channel",6 "stophy_get_playlist",7 "stophy_get_suggestions",8 "stophy_get_credits"9 ]10}What you get
Hosted or local
Use the hosted HTTP endpoint with Bearer auth, or run @stophy/mcp locally when your client expects a subprocess.
Six YouTube tools
Search, video details, transcripts, comments, channels, playlists, suggestions, and a free credits check.
Same API underneath
MCP tools use the same validation, credit metering, refunds, and response shapes as the REST API.
Agent-native setup
One JSON block in Cursor or Claude Desktop. One claude mcp add command in Claude Code. No custom integration code.
Common use cases
- Let Claude search YouTube and pull transcripts while you debug code
- Give Cursor access to channel catalogs when researching a topic
- Wire Windsurf into a video QA workflow without writing HTTP glue
- Check credit balance from inside an agent session before a long run
Frequently asked questions
- Should I use hosted MCP or the local npm server?
- Prefer hosted HTTP when your client supports Streamable HTTP MCP with custom headers. It keeps your key out of subprocess env files and avoids running npx on every session. Use the local npm server when your client only supports stdio MCP.
- How do I pass my API key?
- For hosted MCP, send Authorization: Bearer st_xxx on each request. For the local server, set STOPHY_API_KEY in the MCP config env block or in your shell before starting npx @stophy/mcp.
- Which MCP clients are supported?
- Claude Desktop, Claude Code, Cursor, VS Code, and Windsurf are documented on docs.stophy.dev/mcp. Any client that supports MCP tools can connect via hosted HTTP or the local npm package.
- Do MCP tool calls cost credits?
- Yes. Each data tool call costs one credit, same as the REST API. stophy_get_credits is free.