A
licenseNot graded
qualityD
maintenanceEnables interaction with Notion workspaces through the Notion API. Provides tools to search, read, create, and update Notion pages and databases with real-time synchronization.
1,527
MIT
smithery-notion
by ai.smithery
Server Details
A Notion workspace is a collaborative environment where teams can organize work, manage projects,…
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- smithery-ai/mcp-servers
- GitHub Stars
- 95
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
22 tool updates
- Added
append_blocks - Removed
append-block-children - Added
create_database - Added
create_page - Removed
create-comment - Removed
create-database - Removed
create-page - Added
delete_blocks - Added
get_database - Changed
get_page1 field changed- changed
Input schema / properties / page_id / descriptionPrevious value: -"The ID of the page to retrieve"New value: +"ID of the page to retrieve"
- Removed
get-all-page-comments - Removed
get-block - Removed
get-block-children - Removed
get-comments - Added
list_databases - Removed
list-databases - Added
query_database - Removed
query-database - Changed
search12 fields changed- changed
Input schema / properties / filter / additionalPropertiesPrevious value: -falseNew value: +{} - changed
Input schema / properties / filter / descriptionPrevious value: -"Filter by object type"New value: +"Filter by object type (page or database)" - removed
Input schema / properties / filter / propertiesRemoved value: -{ - "property": { - "const": "object", - "type": "string" - }, - "value": { - "enum": [ - "page", - "database" - ], - "type": "string" - } -} - removed
Input schema / properties / filter / requiredRemoved value: -[ - "value", - "property" -] - removed
Input schema / properties / page_size / defaultRemoved value: -10 - removed
Input schema / properties / page_size / maximumRemoved value: -100 - removed
Input schema / properties / page_size / minimumRemoved value: -1 - changed
Input schema / properties / sort / additionalPropertiesPrevious value: -falseNew value: +{} - changed
Input schema / properties / sort / descriptionPrevious value: -"Sort results"New value: +"Sort by last edited or created time" - removed
Input schema / properties / sort / propertiesRemoved value: -{ - "direction": { - "enum": [ - "ascending", - "descending" - ], - "type": "string" - }, - "timestamp": { - "enum": [ - "last_edited_time" - ], - "type": "string" - } -} - removed
Input schema / properties / sort / requiredRemoved value: -[ - "direction", - "timestamp" -] - added
Input schema / requiredAdded value: +[ + "query" +]
- Changed
update_page1 field changed- changed
Input schema / properties / properties / descriptionPrevious value: -"Properties to update"New value: +"Updated page properties"
- Removed
update-block - Removed
update-database
15 tool updates
- First observed
append-block-children - First observed
create-comment - First observed
create-database - First observed
create-page - First observed
get_page - First observed
get-all-page-comments - First observed
get-block - First observed
get-block-children - First observed
get-comments - First observed
list-databases - First observed
query-database - First observed
search - First observed
update_page - First observed
update-block - First observed
update-database
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
AI workspace for you, your team, and every agent. Tables, docs (images, 4K video), formulas.
AI-native team workspace — tables, documents, workflow automation, live dashboards & analytics
A room-based collaborative platform
Manage tasks, projects, roadmaps, files, meetings, and team workflows with AI tools.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI workflows to integrate with Notion workspaces, supporting page and database creation, queries with filters and sorting, content updates, and workspace-wide search operations.-
- AlicenseNot gradedqualityAmaintenanceNotion-like workspace of pages and customizable databases with a remote MCP server (OAuth 2.1 + PKCE, scoped read/write tokens, full audit log). 14 tools to search, read, and write pages, database rows, and database schemas.70AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with secure access to Notion workspaces, enabling page management, search, block operations, and user management.1,527MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose targeting specific Notion resources and operations. For example, create_page vs. update_page vs. get_page are unambiguous, and query_database vs. list_databases vs. get_database serve different functions. No tools appear to overlap in functionality.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case, such as create_database, get_page, and query_database. This predictability makes it easy for agents to understand and select tools based on their naming conventions.
Tool Count5/5
With 10 tools, this server is well-scoped for Notion operations, covering core CRUD and query functions for pages, databases, and blocks. Each tool earns its place without feeling excessive or insufficient for the domain.
Completeness5/5
The tool set provides complete coverage for Notion's core workflows, including creation, retrieval, updating, deletion, querying, and searching across pages, databases, and blocks. There are no obvious gaps that would hinder agent operations in this domain.