OmniContext
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_TOKEN | No | Your Notion integration token (optional, required only for Notion tools) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Health check — confirms OmniContext is running and returns its version. |
| youtube_get_transcriptA | Fetches the transcript/captions of a YouTube video as plain text. No login or setup required — just paste a video link or ID. |
| youtube_save_transcriptA | Fetches a YouTube video's transcript and writes it to a local .md or .txt file, returning the file path. Use this when the user wants the full transcript exported for later reading, rather than reproduced in the chat. |
| notion_get_pageA | Reads a Notion page's content as markdown. The page must be shared with this integration first (open the page in Notion, click Share, add the integration). |
| notion_searchA | Searches page titles across every Notion page shared with this integration, returning each match's title, ID, and URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.