notion-agent-hub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_API_KEY | Yes | Notion internal integration secret (ntn_...) | |
| OPENAI_API_KEY | No | Optional API key to enable AI content generation | |
| NOTION_DATABASE_ID | Yes | Task database ID |
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 |
|---|---|
| notion-readB | Read pages, databases, or blocks from Notion. Returns structured content including properties and child blocks. |
| notion-writeC | Create or update Notion pages. Supports creating pages with rich content blocks (headings, paragraphs, lists, toggles, code, callouts). |
| notion-queryA | Query a Notion database with filters and sorting. Returns matching pages with summarized properties. |
| web-searchA | Search the web for information. Uses Brave Search API if available, falls back to DuckDuckGo. Useful for research tasks. |
| code-runA | Execute JavaScript code in a sandboxed environment. Has access to Math, Date, JSON, and standard built-ins. No filesystem or network access. |
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
The Notion tools are mostly distinct: notion-read retrieves content, notion-write creates/updates pages, and notion-query filters databases. There is slight overlap between notion-read and notion-query when reading database contents, but descriptions clarify that query is for filtered/sorted lookups. Web-search and code-run are completely separate domains, so misselection is unlikely.
Tool names follow a readable lowercase-with-hyphen style, and verbs are action-oriented (read, write, query, search, run). However, the prefix convention is inconsistent: Notion tools use 'notion-' while web-search and code-run do not. This mixed pattern makes it less predictable than a uniform verb_noun scheme.
With 5 tools, the server is appropriately scoped for a small agent hub. Each tool serves a clear purpose, and the count is neither too thin nor bloated. Slightly more Notion-specific tools could be justified, but the current number feels reasonable.
The Notion tools cover core operations (read, write/update, query), but delete and block-level editing are missing, which could be a dead-end for some workflows. Web-search and code-run add generality but do not fill Notion-specific gaps. Overall, the surface is functional but not fully comprehensive for a Notion agent.