TestingOps.ai

MCP tools for agents · MCP tool for agents

Supabase and TestingOps: read-only test data checks for agents

Connect Supabase's MCP server in read-only mode and TestingOps agents can check the data and logs of your test projects before and after a run.

  • MCP tool for agents
  • Available
Request a demo Supabase MCP server
Connection
MCP tool for agents
Writes back
Nothing, its tools only read
Last checked
7 Nov 2026

In short

Supabase and TestingOps in short

The Supabase connection is an MCP tool for TestingOps agents, set up with a Supabase personal access token; TestingOps connects with read_only=true, so agents can query but not change your data.

Agents can check that the users, orders or other rows a case needs exist before a run, confirm what a run wrote, and read logs when a step failed.

Connect test projects, not production, because the token reaches every project you scoped it to.

What it does

What it does for your testing

  1. 1

    Preconditions checked in the database

    Input
    The test data a case depends on
    TestingOps
    Agents can query the test project for the rows the case needs, such as an active test user
    Output
    A missing precondition found before the run, not halfway through it
  2. 2

    What the run really wrote

    Input
    The expected effect of a case, such as a new order
    TestingOps
    Agents can query the table after the run
    Output
    A check of the stored result, not only of what the screen showed
  3. 3

    Logs for a failed step

    Input
    A failed step against a Supabase backend
    TestingOps
    Agents can read the project's logs for that time
    Output
    The database or API error behind the failure

Step by step

How it works

  1. Create a scoped, read-only tokenIn Supabase, generate a personal access token under Account → Access Tokens, limited to the test projects agents may reach, with Read permissions and an expiry of up to one year.
  2. Connect it in TestingOpsPick Supabase under Extra tools your agents may use in Integrations → API & MCP, paste the token into Supabase access token and select Connect.
  3. Read-only by defaultTestingOps connects to https://mcp.supabase.com/mcp?read_only=true, so Supabase's server runs queries in read-only mode.
  4. Agents query during a taskAn agent can call Supabase tools through TestingOps when a case needs a data check; the token stays on the TestingOps server.

Pinning the connection to one project needs Supabase's project_ref address under Your own MCP server, which cannot carry the token yet. Scope the token to your test projects instead.

Connect

Setup

  1. In Supabase, open Account → Access Tokens and select Generate new token.
  2. Choose the test projects (or organizations) the token may reach, give it Read permissions only and set an expiry of up to one year; copy the token (sbp_…), which is shown once.
  3. In TestingOps, as customer admin, open Integrations → API & MCP and pick Supabase under Extra tools your agents may use (outgoing, over MCP).
  4. Paste the token into Supabase access token and select Connect.

Documentation: Supabase MCP server

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

Use cases

Use cases

Check a test user before a login case

Trigger
A login case keeps failing with a user-not-found message
Uses
The auth and profile tables of the test project
Agent activity
Can query whether the test user exists and is active
Result
A data problem found instead of a false defect
Condition
The token must reach the test project

Confirm an order was stored correctly

Trigger
A checkout case passes on screen
Uses
The orders table
Agent activity
Can query the new order and compare status and amount with the case
Result
A stored-data check after the UI check

Find the error behind a failed API step

Trigger
An API step returns a server error
Uses
Supabase logs for the project
Agent activity
Can read the logs around the failure
Result
The database error to quote in the analysis

Capabilities

Capabilities and limits

What is read

Tables, schema and logs of the Supabase projects your token reaches, through Supabase's read-only mode

What is produced

Data checks and log context in agents' analysis; nothing is stored in TestingOps by the tool itself

Where it can write

Nothing: the connection uses Supabase's read_only=true mode, so seeding or changing data is not possible through it.

How it connects

Supabase's hosted MCP server (https://mcp.supabase.com/mcp?read_only=true) with your personal access token in the Authorization header

Account and permissions

  • A Supabase personal access token (sbp_…) scoped to your test projects, with Read permissions
  • Customer admin (or Manage integrations) rights in TestingOps; the tool is visible only to agents working on your organisation's projects

Limits

  • The token reaches every project it is scoped to; this entry cannot pin one project
  • A scoped token cannot be edited later in Supabase: delete it and create a new one
  • Agents running on Grok receive no MCP tools

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team's mobile app uses Supabase, with a separate test project. They create a token limited to the test project with Read permissions and connect Supabase in TestingOps.

When the reorder-last-purchase case fails, the analysing agent can query the test project and finds that the test user has no previous order, so the analysis asks for test data instead of filing a defect.

Frequently asked questions

Can agents seed test data in Supabase?

Not through this connection. It uses Supabase's read-only mode, so agents can check data but not insert or change it.

Should we connect production?

No. Create the token for your test projects only; it reaches every project you scope it to.

Can we limit the connection to one project?

Scope the token to that project. Supabase's project_ref address would have to go under Your own MCP server, which cannot carry the token yet.

Does TestingOps keep copies of our tables?

No. Agents query when a task needs it; the tool imports nothing into TestingOps.

Next step

Request a demo with a Supabase test project to see agents check data before and after a run.

Request a demoMore mcp tools integrations