monday + Muse

Connect monday to Muse Prepare a grounded board progress briefing

Read board items with Muse and Agent200. Prepare a board progress briefing using the connected user’s own monday account.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. monday tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Use Muse to prepare a short board progress briefing for review. Put the Agent200 key in Muse’s secure credential interface, then inspect the source before sharing the result.

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
Muse · Agent app, through MCP
Authentication
Managed OAuth, per end user
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.
  • Muse, with custom MCP servers allowed. Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

Connect monday to Muse

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page and store it securely.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Create the custom connector

    Connect to https://api.agent200.com/mcp/ over Streamable HTTP with an Authorization: Bearer header. Enter the key in Muse’s secure credential interface.

    Muse chat
    MCP: message that asks Muse to create the custom connector
    Create a Custom Connector for the Agent200 remote MCP server and connect to it:
    Name: Agent200
    Transport: remote streamable HTTP
    URL: https://api.agent200.com/mcp/
    Auth: API key sent in the Authorization header as "Bearer <key>"
    Open the secure credentials store so I can enter the API key there, not in this chat.
    Then list its tools to confirm the connection works.
  3. 3

    Step 3: Inspect read tools

    Confirm the monday operations and schemas advertised by the connection.

  4. 4

    Step 4: Authorize monday

    Connect the intended user and test one accessible board item.

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.

Read the SDK docs

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 Muse.

Agent brief
Goal: connect monday to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/monday/framework/muse/

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 Muse'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 Muse: 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 Muse'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/muse.md

monday tools Muse can call

  • List boards

    Read
    monday_list_boards

    Find boards visible to the connected user.

  • Read a board

    Read
    monday_get_board

    Retrieve one identified board and its fields.

  • List items

    Read
    monday_list_items

    Find items on an accessible board.

  • Read an item

    Read
    monday_get_item

    Retrieve one identified item and column values.

  • Search items

    Read
    monday_search_items

    Search accessible items with a scoped query.

How it works

  1. 01

    You ask Muse

    In your own words, for something in monday.

  2. 02

    Muse picks a tool

    It sees the monday tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    With your own monday connection, within the tools and scopes your project allows.

  4. 04

    Muse 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.

Use monday with another framework

200 OK

monday, connected to Muse.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)