"notion" matching MCP servers:

Enables MCP clients to access Notion through a permission-checking proxy that restricts operations to a configured root page and its subtree, while blocking unauthorized tools. It also handles Notion OAuth and validates signed permission settings.

Enables Claude Desktop and custom AI agents to securely access enterprise Postgres databases and Notion knowledge bases via MCP, with read-only SQL enforcement, audit logging, and API-key authentication.

OAuth token broker for AI agents to securely act on a user's behalf across third-party APIs (Gmail, Slack, GitHub, Notion, etc.) by vaulting tokens server-side and never exposing them to the LLM.

A self-hosted MCP bridge that enables Notion AI to interact with approved Git repositories and curated GitHub APIs, supporting guarded code changes, pull requests, issues, Actions, logs, releases, secret scanning, and audit logging.

A general-purpose MCP connectivity layer that bridges MCP clients to authenticated remote MCP servers, managing authentication, credentials, routing, and connection lifecycle. It enables clients like OpenHands Cloud to securely connect to remote MCP servers such as Notion.

Permission gateway that hands an AI agent a scoped MCP endpoint instead of an OAuth token: connect 27 services (Gmail, Google Calendar/Drive/Ads/Search Console, Slack, Notion, GitHub, Jira, Salesforce, HubSpot, Stripe, LinkedIn, X, Meta Ads and more), grant per-action permissions finer than native OAuth scopes, audit every call and revoke a key in one click. Self-hostable, MIT.

A spec-compliant remote MCP server with built-in OAuth 2.1 and Dynamic Client Registration, enabling Notion Custom Agents to connect via 'Sign in with OAuth' without bearer tokens. It supports SSO federation to Google and Microsoft Entra, and includes basic tools like whoami, echo, and slow_task.