Content Tools
videosearch.io
MCP server for VideoSearch.io that lists supported video platforms and builds search URLs for video queries across them.
ENDPOINT 1
https://videosearch.io/mcp
MCP server metadata
- Name
- videosearch
- Version
- 1.0.0
VideoSearch.io searches videos on 21 platforms (YouTube, TikTok, X, Instagram, Bilibili, Netflix and more) through Google Programmable Search. Call list_video_platforms for platform ids, then get_video_search_url for a page that shows the results in a browser. There is no result-list API.
Known tools 2
list_video_platformsList the video platforms and platform groups VideoSearch.io can search, with each one's id and page URL.
Inferred read-onlyget_video_search_urlBuild the VideoSearch.io page URL that searches videos for a query on one platform or group.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.videosearch]
url = "https://videosearch.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"videosearch": {
"type": "http",
"url": "https://videosearch.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: videosearch
Remote MCP URL: https://videosearch.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"videosearch": {
"url": "https://videosearch.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"videosearch": {
"type": "http",
"url": "https://videosearch.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "videosearch",
"transport": "streamable-http",
"url": "https://videosearch.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.