VideoSeek MCP — Find anything in any video. Semantic video search, video Q&A, persistent memory, and social media import for AI agents.
Videoseek MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Videoseek MCP directly instead of describing what you should do. VideoSeek MCP — Find anything in any video. Semantic video search, video Q&A, persistent memory, and social media import for AI agents.
Give your AI agent (Claude, Cursor, Windsurf, etc.) the ability to:
Once Videoseek MCP is connected, these are the calls the assistant has available:
Cursor — The Cursor tool exposed by this serverSearch — The Search tool exposed by this serverYou will need 2 environment variables: MEMORIES_API_KEY, MEMORIES_UNIQUE_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Videoseek MCP's toolset — Cursor, Search — is a fair guide to whether it matches your workflow. It is maintained by kennyzheng-builds; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cursor | The Cursor tool exposed by this server. |
| Search | The Search tool exposed by this server. |
{
"mcpServers": {
"videoseek": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"MEMORIES_API_KEY": "your-value",
"MEMORIES_UNIQUE_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MEMORIES_API_KEY | Credential the server authenticates with. | Yes |
| MEMORIES_UNIQUE_ID | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.