OmniContext
Connects Claude Desktop to Notion and YouTube transcripts with one-click installation, enabling natural language queries about your pages and video content.
README
OmniContext
Connect Claude to your life — without touching a terminal.
<!-- INSERTA AQUÍ EL GIF DE DEMOSTRACIÓN -->
OmniContext is a local MCP server for Claude Desktop that connects Claude to the tools you already use — Notion and YouTube today, more on the way. Install it as a one-click extension, no terminal or API dashboard required.
You: Summarize this video for me: youtube.com/watch?v=xxxxxxxxxxx
Claude: [reads the transcript through OmniContext and replies instantly]
You: What does my Notion page "Q3 Roadmap" say about launch dates?
Claude: [searches your Notion, opens the page, answers from its content]
Features
- Notion, without the copy-pasting — search page titles and pull full page content as clean markdown, right from the conversation.
- YouTube videos, the moment you paste the link — Claude reads the transcript and can summarize, analyze, or answer questions about it instantly.
- Clean transcript exports — when you want the raw text (for notes, research, or another tool), OmniContext saves it as a tidy
.mdfile instead of dumping it into the chat.
More integrations are on the way — see the Roadmap.
Installation
No code, no terminal, no API dashboard.
- Download the latest
omnicontext.mcpbfrom the Releases tab. - Open Claude Desktop → the menu (☰) →
File → Settings → Extensions. - Click Advanced settings then scroll down to Install Extension… and select it.
- Using Notion? Paste your integration token into the form Claude Desktop shows you. That's the entire setup.
- Try it in a chat:
- "What's this YouTube video about:
<link>" - "Read my Notion page:
<link>"
- "What's this YouTube video about:
Note: your Notion token is stored encrypted by your OS (Keychain on macOS, Credential Manager on Windows) — never in a plain text file. If you don't need Notion, skip it; the YouTube tools work with zero setup.
Development
For running the server from source, contributing, or wiring it into Claude Code instead of Claude Desktop.
git clone <your-repo-url>
cd omnicontext
npm install
npm run build # compiles TypeScript -> dist/
npm test # full suite, incl. live smoke tests
npm run pack # builds omnicontext.mcpb locally
Register it with Claude Code:
claude mcp add --transport stdio omnicontext \
--env NOTION_TOKEN=your_notion_token \
-- node /absolute/path/to/omnicontext/dist/index.js
Run it directly during development:
npm run dev
Debug tool calls with the official MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.js
Tools reference
| Tool | What it does |
|---|---|
notion_get_page |
Reads a Notion page (URL or ID) and returns it as markdown |
notion_search |
Searches page titles across everything shared with the integration |
youtube_get_transcript |
Fetches a YouTube video's transcript as plain text, for in-chat analysis |
youtube_save_transcript |
Saves a video's full transcript to a local .md file |
Roadmap
OmniContext is an early MVP — the foundation is in place, and the integrations list is just getting started.
- [x] YouTube transcripts (in-chat + file export)
- [x] Notion (internal token, read-only)
- [x] One-click
.mcpbpackaging for Claude Desktop - [ ] Notion OAuth — one-click connect, no more manual tokens or sharing pages by hand
- [ ] Discord integration
- [ ] Telegram integration
- [ ] More integrations, one context source at a time
Privacy & security
OmniContext runs entirely on your machine. It talks directly to Notion's and YouTube's own APIs — there is no OmniContext backend, no analytics, and no middleman server that sees your data.
Contributing
Issues and pull requests are welcome. If you're adding a new integration, follow the existing pattern in src/integrations/<name>/ — each one is self-contained and registers its own tools without touching the core server.
Support
Found a bug or want to request an integration? Open an issue.
License
MIT — free to use, modify, and self-host.
Built on the Model Context Protocol.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.