Koskamo

Vidskim MCP

A remote MCP server that allows AI assistants to read YouTube video transcripts with clickable timestamps, search within videos, retrieve video metadata, and list channel videos. It supports OAuth 2.1 authentication via Google sign-in and provides tools for summarization, research, and content creation based on actual video captions.

Visit Vidskim

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Vidskim MCP logo, by VidskimVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by Vidskim
You need:Google sign-inNo API key
MCP endpoint (Streamable HTTP)
https://vidskim.com/api/mcp
Vendor documentation

What you can do with it

  • Summarize lectures as study notes with timestamps
  • Turn interviews into social media posts with exact quotes
  • Follow coding tutorials or conference talks via agent
  • Search for specific topics or quotes inside a video

Source and maintenance

Vendor evidenceRegistry 1.0.2
mcp-registry: com.vidskim/youtube@1.0.2Source repositoryProject website
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
521 ms
95th percentile latency
521 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 521 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http vidskim-mcp https://vidskim.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add vidskim-mcp --url https://vidskim.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vidskim-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "vidskim-mcp": {
      "url": "https://vidskim.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "vidskim-mcp": {
      "type": "streamableHttp",
      "url": "https://vidskim.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vidskim-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "vidskim-mcp": {
      "type": "http",
      "url": "https://vidskim.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http vidskim-mcp https://vidskim.com/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "vidskim-mcp": {
      "url": "https://vidskim.com/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "vidskim-mcp": {
      "serverUrl": "https://vidskim.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Vidskim MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,350

Do you run Vidskim MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing