Check for a known bug first
- Trigger
- A case fails in a way that may already be reported
- Uses
- The team's bug board
- Agent activity
- Can search the board's items for the same symptom
- Result
- A link to the existing item in the analysis
MCP tools for agents · MCP tool for agents
monday.com and TestingOps: bug boards and items for agents
Connect monday.com's MCP server and TestingOps agents can read your boards and docs and, with approval, record defects on the board your team works from.
- MCP tool for agents
- Available
monday.com
AnswerTool call
TestingOpsAI test agents
- Connection
- MCP tool for agents
- Writes back
- Only after a person approves
- Last checked
- 7 Nov 2026
In short
monday.com and TestingOps in short
The monday.com connection is an MCP tool for TestingOps agents, set up with a personal API token, so agents can call monday.com's hosted MCP server and work with the boards, items and docs that token's user can see.
Agents can check a bug board for an existing item before reporting a failure, read a release board while planning a run, and create or update items when the call is approved.
The token carries its user's full permissions, so connect an account that sees only the boards agents need.
What it does
What it does for your testing
- 1
Duplicates caught on the bug board
- Input
- A failure an agent is about to report
- TestingOps
- Agents can search the bug board for an item that describes the same problem
- Output
- An existing item referenced instead of a new duplicate
- 2
Release scope from your boards
- Input
- A release or sprint board
- TestingOps
- Agents can read which items are in the release
- Output
- Test planning that follows what your team is shipping
- 3
Defects on your board, with approval
- Input
- A confirmed defect
- TestingOps
- Agents can request a new item with steps and evidence; the call waits for approval
- Output
- A bug board item created after approval
Step by step
How it works
- Copy a personal API tokenIn monday.com, open your profile picture → Developers and copy the token under My access tokens (older accounts: API token). Admins also find it under Administration → Connections → Personal API token.
- Connect it in TestingOpsPick monday.com under Extra tools your agents may use in Integrations → API & MCP, paste the token into monday.com API token and select Connect.
- Reads open, writes ask firstReading boards and items is open to agents; every tool that is not marked read-only or named for reading asks first, and tools that delete also need a formal approval.
- Agents use the boards during a taskAn agent can search and read items when it analyses a failure or plans a run; the token stays on the TestingOps server.
monday.com has no built-in TestingOps integration, so this MCP tool is how agents reach it. Teams on Jira, GitHub, GitLab, Azure DevOps, Linear or YouTrack use the built-in integrations under Project tools.
Connect
Setup
- In monday.com, click your profile picture and choose Developers; in the Developer Center open My access tokens (older accounts: API token), select Show and copy the token.
- In TestingOps, as customer admin, open Integrations → API & MCP and pick monday.com under Extra tools your agents may use (outgoing, over MCP).
- Paste the token into monday.com API token and select Connect.
Documentation: monday.com MCP with an API token
Use cases
Use cases
Plan the regression run from the release board
- Trigger
- A release is being prepared
- Uses
- The release board and its items
- Agent activity
- Can read which items the release contains
- Result
- A run focused on the changed areas
Report a confirmed defect on the bug board
- Trigger
- A failure is confirmed as a product defect
- Uses
- Item creation on the bug board
- Agent activity
- Can request an item with steps, expected and actual results
- Result
- A new item on the board after approval
- Condition
- Approval by someone in your organisation with Manage integrations rights (or the TestingOps team)
Capabilities
Capabilities and limits
What is read
Boards, items, updates and docs the token's user can see
What is produced
Context for agents' analysis and planning; nothing is stored in TestingOps by the tool itself
Where it can write
Items and updates on your boards, through monday.com's write tools. Each call asks first and waits for approval from someone in your organisation with Manage integrations rights (or the TestingOps team).
How it connects
monday.com's hosted MCP server (https://mcp.monday.com/mcp) with the personal API token in the Authorization header
Account and permissions
- A personal API token of an account that sees only the boards agents need; the token carries that user's full permissions
- Customer admin (or Manage integrations) rights in TestingOps; the tool is visible only to agents working on your organisation's projects
Limits
- A tool runs without asking only when monday.com marks it read-only or its name says it reads; every other tool asks first
- Personal tokens are tied to one user's permissions
- Agents running on Grok receive no MCP tools
Example
Example: how a team uses it
Illustrative scenario, not a customer story.
A team plans its work and tracks bugs in monday.com. They create a dedicated monday.com account that sees only the Bugs and Releases boards and connect its token in TestingOps.
When a nightly run fails on the coupon field, the agent can search the Bugs board, finds an open item for the same problem and references it in its analysis instead of drafting a new defect.
Frequently asked questions
Why use a dedicated monday.com account?
The personal token carries all of its user's permissions. An account that sees only the boards agents need keeps the connection limited.
Can agents create items on our boards?
Yes, through monday.com's create and update tools, but each call asks first and waits for approval on the request from someone in your organisation with Manage integrations rights (or the TestingOps team).
Why is monday.com an MCP tool and not a tracker integration?
TestingOps has built-in integrations for Jira, GitHub, GitLab, Azure DevOps, Linear and YouTrack. monday.com has none, so agents reach it through monday.com's own MCP server.
Does TestingOps sync our boards?
No. Agents read and write through the tool during a task; there is no background sync.
Related integrations
Jira
Stories and acceptance criteria become test context; agents act on the workflow steps you choose and report back on the issue.
Native connectionAvailableLinear
A team's issues become test context; agents read and update issues, and defects become Linear issues.
Native connectionAvailableZapier
Agents can run the Zapier actions you enable on your Zapier MCP server, in the apps connected to Zapier.
MCP tool for agentsAvailable
Next step
Request a demo to see agents check your monday.com bug board before they report a failure.