OmniContext
# OmniContext
Connect Claude to your life — without touching a terminal.
<!-- INSERTA AQUÍ EL GIF DE DEMOSTRACIÓN -->



[](LICENSE)
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 `.md` file instead of dumping it into the chat.
More integrations are on the way — see the [Roadmap](#roadmap).
---
## Installation
No code, no terminal, no API dashboard.
1. Download the latest `omnicontext.mcpb` from the [Releases](../../releases) tab.
2. Open Claude Desktop → the menu (☰) → `File → Settings → Extensions`.
3. Click Advanced settings then scroll down to *Install Extension…* and select it.
4. Using Notion? Paste your integration token into the form Claude Desktop shows you. That's the entire setup.
5. Try it in a chat:
- "What's this YouTube video about: `<link>`"
- "Read my Notion page: `<link>`"
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.
```bash
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:
```bash
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:
```bash
npm run dev
```
Debug tool calls with the official [MCP Inspector](https://github.com/modelcontextprotocol/inspector):
```bash
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 `.mcpb` packaging 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](../../issues).
---
## License
[MIT](LICENSE) — free to use, modify, and self-host.
---
Built on the [Model Context Protocol](https://modelcontextprotocol.io).
TDQS
Scored across 5 tools
All tools have clearly distinct purposes: Notion page reading and searching, a health check, and YouTube transcript retrieval and saving. No overlap or ambiguity.
Tool names follow a consistent verb_noun pattern with snake_case (notion_get_page, notion_search, youtube_get_transcript, youtube_save_transcript) except for 'ping', which is a standard health check name and does not disrupt consistency.
With 5 tools covering two distinct domains (Notion and YouTube) plus a health check, the count is well-scoped and appropriate for the server's purpose.
The Notion integration is limited to reading and searching, missing create/update/delete operations. YouTube tools only handle transcripts, lacking search or video metadata. Significant gaps exist for full workflow coverage.