Does vidIQ have an MCP server?
vidIQ maintains an official MCP server.
- Access
- Remote server
- Endpoint
- https://mcp.vidiq.com/mcp
- Category
- Social Media
A remote server run by vidIQ itself — nothing to install. Documented at vidiq.com.
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http vidiq https://mcp.vidiq.com/mcpAdd --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://mcp.vidiq.com/mcp - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"vidiq": {
"url": "https://mcp.vidiq.com/mcp"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"vidiq": {
"type": "http",
"url": "https://mcp.vidiq.com/mcp"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://mcp.vidiq.com/mcp - Complete sign-in, then enable the connector in a new chat
Does vidIQ have an official MCP server?
Yes. vidIQ maintains an official MCP server, hosted at https://mcp.vidiq.com/mcp.
How do I connect vidIQ to Claude?
Add https://mcp.vidiq.com/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http vidiq https://mcp.vidiq.com/mcp" in Claude Code.
Do I need to install anything to use the vidIQ MCP server?
No. It is a remote server hosted by vidIQ, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
Published to the MCP Registry under vidIQ's verified namespace com.vidiq and described on vidIQ's own page vidiq.com/mcp; mcp.vidiq.com/mcp answers MCP initialize with 401 (authorization required). GitHub metadata is refreshed every six hours.
Published to the MCP Registry under vidIQ's verified namespace com.vidiq and described on vidIQ's own page vidiq.com/mcp; mcp.vidiq.com/mcp answers MCP initialize with 401 (authorization required).
- github data refreshed 2026-09-29, then every 6 hours
- vendor docs verified on 2026-09-29
Spotted something out of date? Tell us — corrections ship same-day.