monday + Claude Duet
Connect monday to Claude Duet
Prepare a grounded board progress briefing
Read board items with Claude Duet and Agent200. Prepare a board progress briefing using the connected user’s own monday account.
On this page
Overview
Request an on-demand board progress briefing in Claude Duet. Ask it to name retrieved sources and missing information. This request does not establish continuous monitoring.
Start with one identified board item. Preserve returned board, item, status and date fields; report missing data and keep the workflow read-only.
Provider reference: monday API.
- Connector
- monday
- Works with
- Claude Duet · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 5 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- monday enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a monday account. They approve access once, on monday's own page.
- Claude Duet, with custom MCP servers allowed. Claude Duet is a research preview for Pro, Max and Ultra users in the US, by invitation. It uses the connectors of your Claude account, and sending an API key needs Claude's Request headers option.
Connect monday to Claude Duet
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude Duet in the next step, as "Authorization: Bearer <your key>". One key covers monday and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Add Agent200 as a custom connector in Claude
Duet has no connector settings of its own: it uses those of your Claude account. In Claude, go to Customize > Connectors, choose Add > Add custom connector, enter the server URL, choose No sign-in and add the
authorizationrequest header withBearerand your key.Add custom connectorMCP: Claude custom connector (URL and request header) Remote MCP server URL: https://api.agent200.com/mcp/ Authentication: No sign-in Request header name: authorization Value: Bearer YOUR_AGENT200_API_KEY -
3
Step 3: Use it from Duet
Open Claude Duet with the same Claude account. The connectors set up in Claude are there from your first message; manage them in your Claude settings.
-
4
Step 4: Approve actions when Duet asks
Duet asks before it sends a message, pays, signs or deletes anything. If you cannot approve right away, it finishes the rest and brings the approval back later.
-
5
Step 5: Connect your monday account
The first time you ask Claude Duet for something in monday, Agent200 returns an authorization link. Open it and approve access on monday's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude Duet or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Read the monday board item I identify and prepare a board progress briefing. Name the source and use only board, item, status and date fields. State access gaps; do not change records.
What should come back
- The selected board item is identified.
- Only the returned board, item, status and date fields are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected board item ID, account scope, read permission and pagination. Column meanings are board-specific. Resolve status labels and pagination from the selected board; search is result-limited.
Get your API key
Create a key in the Agent200 dashboard. It reaches monday and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect monday to Claude Duet.
Goal: connect monday to Claude Duet with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/monday/framework/claude-duet/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude Duet's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure monday is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Claude Duet: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude Duet's exact menus or commands. 4. The first monday request returns an authorization link if the user has not connected monday yet: show it to them and continue once they have approved access on monday's own page. 5. Check it works with this request: "Read the monday board item I identify and prepare a board progress briefing. Name the source and use only board, item, status and date fields. State access gaps; do not change records." What should come back: - The selected board item is identified. - Only the returned board, item, status and date fields are reported. - Access gaps and missing context are explicit; no source data is changed. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in monday, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/monday/framework/claude-duet.md
monday tools Claude Duet can call
-
List boards
Readmonday_list_boardsFind boards visible to the connected user.
-
Read a board
Readmonday_get_boardRetrieve one identified board and its fields.
-
List items
Readmonday_list_itemsFind items on an accessible board.
-
Read an item
Readmonday_get_itemRetrieve one identified item and column values.
-
Search items
Readmonday_search_itemsSearch accessible items with a scoped query.
No tool matches that search.
How it works
-
01
You ask Claude Duet
In your own words, for something in monday.
-
02
Claude Duet picks a tool
It sees the monday tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own monday connection, within the tools and scopes your project allows.
-
04
Claude Duet answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's monday account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and monday enforces what its API grants.
Troubleshooting
The source cannot be read
Check the selected board item ID, account scope, read permission and pagination. Column meanings are board-specific. Resolve status labels and pagination from the selected board; search is result-limited.
FAQ
How do I verify this result?
Compare the named board item and returned board, item, status and date fields with the source. Treat missing information as missing, not as a fact.
