TestingOps.ai

MCP tools for agents · MCP tool for agents

Notion and TestingOps: specs and decisions in Notion for agents

Sign in to Notion's MCP server and TestingOps agents can search and read the specs, release notes and decisions your team writes in Notion while they design test cases.

  • MCP tool for agents
  • Available with limits
Request a demo Notion MCP
Connection
MCP tool for agents
Writes back
Only after a person approves
Last checked
7 Nov 2026

In short

Notion and TestingOps in short

The Notion connection is an MCP tool for TestingOps agents: you sign in on Notion's screen, choose the pages and databases to share, and agents can then call Notion's hosted MCP server.

Agents can search and read those pages, data sources and comments, for example the spec of a feature they write cases for, while creating, updating, moving or duplicating pages and adding comments ask for approval first.

Notion pages are read live during a task and are not imported into the TestingOps knowledge base, and the sign-in has not yet been confirmed end to end on TestingOps cloud.

What it does

What it does for your testing

  1. 1

    Specs read where they are written

    Input
    A feature spec or product requirements page in Notion
    TestingOps
    Agents can search Notion and read the page while writing cases for the feature
    Output
    Cases that refer to the spec your team maintains
  2. 2

    Open questions found early

    Input
    Comments and linked pages around a spec
    TestingOps
    Agents can read the comments and related pages
    Output
    Questions to settle before cases are finalised
  3. 3

    Test notes back in Notion, with approval

    Input
    A summary an agent wants to add to a release page
    TestingOps
    TestingOps asks for approval before any page is created or updated
    Output
    A Notion page or comment written only after approval

Step by step

How it works

  1. Start the sign-inUnder Integrations → API & MCP, pick Notion in Extra tools your agents may use and select Continue to sign-in. TestingOps registers itself with Notion.
  2. Share what agents may seeOn Notion's screen, choose the pages and databases to share. Agents can reach only what you share there.
  3. Reads open, writes listedTestingOps keeps an explicit list of Notion's tools: search and fetch tools are reads, and tools that create, update, move or duplicate pages, comments, databases or views ask first.
  4. Agents read during a taskWhen a task needs a spec, an agent can search and read it through TestingOps; the sign-in stays on the TestingOps server.

Notion's sign-in returns to your TestingOps address, which must use https.

Connect

Setup

  1. In TestingOps, as customer admin, open Integrations → API & MCP and pick Notion under Extra tools your agents may use (outgoing, over MCP).
  2. Select Continue to sign-in, sign in to Notion and choose the pages and databases agents may use.
  3. Back in TestingOps, check that the row lists Notion's tools; if it shows Sign-in not finished, select Finish sign-in.

Documentation: Notion MCP

Where you connect it in TestingOps: Integrations → API & MCP → Extra tools your agents may use → Notion

Use cases

Use cases

Write cases from a Notion spec

Trigger
A feature is specified in a Notion page
Uses
The spec page and its linked pages
Agent activity
Can read the acceptance criteria and edge cases in the spec before drafting cases
Result
Draft cases that cite the spec page
Condition
The page must be shared at Notion's sign-in

Check a release page before a regression run

Trigger
The team keeps release notes in a Notion database
Uses
The release database
Agent activity
Can read which features changed in the release
Result
A list of areas to put first in the regression run

Leave a test summary on a release page

Trigger
A release run finishes
Uses
The release page and Notion's comment tool
Agent activity
Can request a comment with the run summary, which is written after approval
Result
A summary next to the release notes
Condition
Approval by someone in your organisation with Manage integrations rights (or the TestingOps team)

Capabilities

Capabilities and limits

What is read

The pages, databases, data sources, views, comments, users and meeting notes shared at Notion's sign-in

What is produced

Context for agents' test design; nothing is stored in TestingOps by the tool itself

Where it can write

Pages, comments, databases, data sources and views in Notion, and moving or duplicating pages. All of these are on TestingOps' explicit write list, so each call asks first and waits for approval from someone in your organisation with Manage integrations rights (or the TestingOps team).

How it connects

Notion's hosted MCP server (https://mcp.notion.com/mcp) through an OAuth sign-in; TestingOps registers itself with Notion

Account and permissions

  • A Notion account that can share the relevant pages and databases
  • Customer admin (or Manage integrations) rights in TestingOps; the tool is visible only to agents working on your organisation's projects

Limits

  • Access is what you share at Notion's sign-in; TestingOps does not narrow it further
  • Your TestingOps address must use https for the sign-in to complete
  • A real sign-in on TestingOps cloud has not been confirmed end to end yet
  • Not imported into the knowledge base: agents read Notion live during a task
  • Agents running on Grok receive no MCP tools

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A product team writes its specs in Notion. The QA lead signs in to Notion from TestingOps and shares the team's Specs database.

When a new gift card balance feature reaches testing, the agent can read its spec, notices an open comment about expired cards and adds a question about it to its draft cases instead of guessing the expected behaviour.

Frequently asked questions

Is Notion imported into the knowledge base?

No. This connection lets agents search and read Notion live during a task; the tool copies nothing into the TestingOps knowledge base.

Can agents edit our pages?

Only after approval. Every Notion tool that creates, updates, moves or duplicates content is on TestingOps' write list, so each call waits for approval from someone in your organisation with Manage integrations rights (or the TestingOps team).

Which pages can agents see?

The pages and databases you share on Notion's sign-in screen. Share only what agents need.

Our self-hosted TestingOps runs on plain http. Will Notion work?

No. Notion's sign-in has to return to an https address.

Next step

Request a demo to see agents read a Notion spec while they draft test cases.

Request a demoMore mcp tools integrations