vidIQ

com.vidiqPublished by vidiq.comOfficial publisherv1.0.0Updated Oct 24, 2026

Research and create for YouTube, Instagram & TikTok

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

vidIQ is a remote MCP server that lets an assistant research and create content for YouTube, Instagram and TikTok.

What you can do
Research content across YouTube, Instagram and TikTok, per the provider's description of the server's purpose. Support creating content for those platforms. No individual tools are listed in the supplied manifest, so specific capabilities are not documented here.
When to use it
Worth considering when you want an assistant to help with social video research or content creation for YouTube, Instagram or TikTok, and you already use or are willing to sign in to vidIQ.
Requirements
A remote streamable HTTP endpoint at mcp.vidiq.com; no local package or runtime is needed. OAuth authentication is required, so a vidIQ account sign-in is expected. No environment variables or headers are declared.
Before you install
Access is tied to a vidIQ account through OAuth, so review what account data and permissions you grant. The description mentions creating content, which may publish or change data on connected platforms; confirm before any write action. No tool-level details are provided, so verify behavior in the provider's own documentation.

Installation

In SourceWeft

  1. Open vidIQ in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.vidiq%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "vidiq": {
      "type": "http",
      "url": "https://mcp.vidiq.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.