Back to integrations

Notion integration for background agents

Enable hosted Notion MCP access for pages, databases, comments, and search.

Integration details

Connection

  • Hosted MCP via Notion MCP OAuth

Agent actions

Notion MCP

  • notion-search

    Search across Notion workspace content and connected sources where available.

  • notion-fetch

    Retrieve Notion page, database, or data source content by URL or ID.

  • notion-create-pages

    Create one or more Notion pages with properties, content, icons, covers, and templates.

  • notion-update-page

    Update a Notion page, including properties, content, icon, cover, or template application.

  • notion-move-pages

    Move one or more Notion pages or databases to a new parent.

  • notion-duplicate-page

    Duplicate a Notion page within the workspace.

  • notion-create-database

    Create a Notion database with an initial data source and view.

  • notion-update-data-source

    Update a Notion data source, including properties, name, and description.

  • notion-create-view

    Create a database view such as table, board, list, calendar, timeline, gallery, form, chart, map, or dashboard.

  • notion-update-view

    Update a Notion database view name, filters, sorts, or display configuration.

  • notion-query-data-sources

    Query across multiple Notion data sources with summaries, grouping, and filters.

  • notion-query-database-view

    Query data from a Notion database using a predefined view.

  • notion-create-comment

    Add comments to Notion pages or selected content.

  • notion-get-comments

    List comments and discussions on a Notion page.

  • notion-get-teams

    Retrieve teams and teamspaces in the current workspace.

  • notion-get-users

    List workspace users and details.

  • notion-get-user

    Retrieve a Notion user by ID.

  • notion-get-self

    Retrieve bot user and connected workspace information.

Credential safety

Credential-less sandboxes

Mistle lets agents access connected services without placing provider credentials inside the sandbox. Approved outbound requests are routed through Mistle's credential proxy, where authentication happens outside the agent runtime.

Credentials stay encrypted in Mistle's control plane and are applied only when a request is authorized for the calling sandbox and organization.

Read the credential-less sandboxes article
Diagram showing sandbox traffic routed through an egress proxy before credential injection.