Skip to main content

Notion MCP

Connect your AI tools to Notion using the Model Context Protocol (MCP) through Cequence AI Gateway. The Notion MCP server gives AI assistants secure access to your Notion workspace for reading and writing pages, databases, and more.

1. Overview​

Notion MCP is a remote, vendor-hosted MCP server provided by Notion. You do not run the server yourself; you connect to it from Cequence AI Gateway using the server URL and OAuth.

  • Server URL: https://mcp.notion.com/mcp
  • Transport: HTTP (Streamable HTTP)
  • Hosted by: Notion

Why use Notion MCP?

  • Easy setup — Connect through simple OAuth, with one-click installation for supported AI tools
  • Full workspace access — AI tools can read and write to your Notion pages just like you can
  • Optimized for AI — Built specifically for AI agents with efficient data formatting

2. Supported authorization types​

TypeSupportedNotes
OAuth 2.0YesRecommended for Cequence AI Gateway. Uses Dynamic Client Registration (DCR); no need to create an OAuth app in Notion.
API key (Internal Integration Secret)YesFor programmatic or integration use. Create an Internal Integration in Notion, then use the API secret as a Bearer token. See Internal Integration setup below.

When you add Notion MCP in Cequence AI Gateway, authentication is typically handled via OAuth 2.0 with Dynamic Client Registration. You sign in with your Notion account and grant access during the gateway flow. If your setup uses an Internal Integration instead, use the API secret as described below.

For security best practices, see Notion MCP security best practices.

3. What can you do with this MCP server​

The Notion MCP server allows AI assistants to:

  • Read and write to your Notion pages and databases
  • Search across your Notion workspace content
  • Create documentation (e.g. PRDs, tech specs, architecture docs)
  • Manage tasks and update project status
  • Build reports (release notes, project updates, performance reports)
  • Plan campaigns (briefs, tracking across marketing channels)

4. Prerequisites​

Before adding Notion MCP in Cequence AI Gateway, ensure you have:

  • Access to Cequence AI Gateway (e.g. beta.aigateway.cequence.ai)
  • A Notion account with access to the workspace(s) you want to use with AI tools. For extended MCP capabilities: Notion AI is required for notion-search to search across connected tools (Slack, Google Drive, etc.); without it, search is limited to the Notion workspace only. The notion-query-data-sources tool requires an Enterprise plan with Notion AI; the notion-query-database-view tool (when query-data-sources is not available) requires a Business plan or higher with Notion AI.
  • For OAuth authentication: an auth app with client credentials (client ID and client secret) in your vendor account, unless the server supports Dynamic Client Registration (DCR). Notion MCP supports DCR, so you typically do not need to create an OAuth app.

5. Example workflows​

  • Create documentation: “Generate a PRD from this research and save it as a new Notion page in [workspace].”
  • Search and answer: “Search my Notion for decisions about the Q2 launch and summarize them.”
  • Manage tasks: “Create a Notion database for this sprint’s tasks and update status for [task name].”
  • Reports: “Create a release notes page in Notion from the last 10 commits in this repo.”

6. Connecting MCP server from Cequence AI Gateway​

  1. Log in to Cequence AI Gateway.
  2. Choose your tenant.
  3. Go to App catalogue.
  4. Filter by Remote MCP server.
  5. Search for Notion MCP and then select it.
  6. Click Create MCP server.
  7. Choose auth method. If OAuth, you need an auth app with client credentials in your vendor account (see Prerequisites).
  8. Complete the setup as prompted, select tools, and deploy.

Use the generated MCP server URL in your client (Claude, Cursor, Windsurf, etc.) as described in the Client Configuration docs. For detailed UI steps and screenshots, see Create a third-party MCP Server.

7. Additional information specific to Notion MCP​

  • Dynamic Client Registration: Notion MCP uses OAuth 2.0 with DCR, so you do not need to create or configure an OAuth app in Notion; the gateway and Notion handle registration.
  • Timeout: The remote server uses a 30-second timeout for requests.
  • Official documentation: For full tool reference, security best practices, and troubleshooting, see the Notion MCP official documentation.

Internal Integration (API key) setup​

If you use API key authorization (Internal Integration Secret) instead of OAuth:

  1. Create your integration at the integrations settings page in Notion. You must be a workspace owner.
  2. Get your API secret from the Configuration tab of your integration. This is your "Internal Integration Secret."
  3. Keep your secret secure — use environment variables and never commit it to version control. If the secret is exposed, refresh it immediately in the integration settings.
  4. Use the token in requests by including it in the Authorization header as a Bearer token: 
    curl 'https://api.notion.com/v1/pages/...' \
      -H 'Authorization: Bearer YOUR_API_KEY' \
      -H 'Notion-Version: 2025-09-03'
  5. Grant page access — Workspace members must explicitly share pages and databases with your integration via Notion’s UI (e.g. open a page → Share → Invite → select your integration) before the integration can access them. The integration only sees content it has been granted access to.