src ▸ site opened 0

Turn monday.com into MCP tools

Give your AI agent monday.com tools. Writ turns your monday.com workflows into authenticated MCP tools your agent can call, taking real actions on your own account.

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
claude_desktop_config.jsonMCP · writ-monday
json
{
  "mcpServers": {
    "writ-monday": {
      "url": "https://api.usewrit.app/mcp/your-workspace",
      "headers": { "Authorization": "Bearer wt_8f2c...a91" }
    }
  }
}
MCP server any client authenticated
new ▸ tool minted 01
02
create

No monday.com MCP server yet? Build one in minutes

Record the monday.com task once, or describe it to an AI session, and Writ turns it into an MCP tool your agent can call, taking real actions on your own monday.com account.

  1. 1
    Record a monday.com action once

    Open the recorder and open a board on monday.com in a real browser. Writ captures the steps, login and 2FA included, into a workflow.

  2. 2
    Publish it as an MCP tool

    One click exposes the workflow as an MCP tool with a typed input schema, alongside a REST endpoint. Your agent picks it by its description.

  3. 3
    Call it from any MCP client

    Point Claude Desktop, Claude Code, Cursor, or any MCP client at your Writ server. The monday.com tool acts on your own account and returns structured output.

Browse supported MCP clients, see what's possible on workflows, or search for another site. Free to start. See pricing.

gap ▸ no official mcp 02
03
why

monday.com has no MCP server

Read-only website-to-MCP tools can summarize a monday.com page, but they can't do anything on it. Writ turns the monday.com workflows you build into MCP tools your agent calls to take real actions (search, extract, submit), authenticated, on your own monday.com account.

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

tools ▸ actions named 03
04
named tools

monday.com tools your agent can call

Each tool is a real monday.com workflow with a typed input schema and structured output. Your agent picks the right one by its description.

{ }monday.export_boardExport the items and columns of a board.

Example tool schema

monday.export_board.jsonschema
json
{
  "name": "monday.export_board",
  "description": "Export the items and columns of a board.",
  "input_schema": {
    "type": "object",
    "properties": {
      "query": { "type": "string", "description": "What to look up on monday.com." }
    },
    "required": ["query"]
  }
}
wire ▸ any client 04
05
connect

Add the server to any MCP client

Copy the config into your client and authenticate with a wt_ key. Tools appear automatically.

Your key (wt_)
json
{
  "mcpServers": {
    "writ-monday": {
      "url": "https://api.usewrit.app/mcp/your-workspace",
      "headers": { "Authorization": "Bearer wt_8f2c...a91" }
    }
  }
}
Downstream caller (csk_)
json
{
  "mcpServers": {
    "writ-monday": {
      "url": "https://api.usewrit.app/mcp/your-workspace",
      "headers": { "Authorization": "Bearer csk_3a90...f4d" }
    }
  }
}
>_

Per-client setup. Step-by-step config for each client lives on the per-client pages: Claude Desktop, Claude Code, Cursor, Windsurf.

auth ▸ logged-in web 05
06
authenticated

Your agent acts on your own monday.com account

Writ signs into your own monday.com account through a Persona, including SSO, and runs inside that session.

PersonasTOTP & mailbox OTP Scoped wt_ / csk_ keysStructured output

Use Writ on your own monday.com account. Authorized automation of your own boards.

faq ▸ questions answered 07
08
faq

monday.com MCP questions

Is there an official monday.com MCP server?
monday.com does not publish an MCP server. Writ lets you turn the monday.com workflows you build (recorded, described, or discovered) into MCP tools your agent can call. They take real actions, not just read page text.
Are there ready-made monday.com MCP tools I can install?
Record the monday.com task once in the recorder, or describe it to an AI session, then publish it. Writ exposes it as both an MCP tool and a REST endpoint, usually in minutes.
How is this different from a read-only website-to-MCP tool?
Most website-to-MCP tools are readability crawlers that return page text. Writ tools act and transact: they log in, fill forms, click, extract, and complete multi-step monday.com tasks, then return structured output your agent can use.
Does it work with monday.com login and 2FA?
Writ signs into your own monday.com account through a Persona, including SSO, and runs inside that session. Because each MCP tool is a real browser workflow, it runs inside your own authenticated monday.com session, with TOTP and mailbox-OTP two-factor handled by Personas.
Which MCP clients can use these monday.com tools?
Any MCP-compatible client: Claude Desktop, Claude Code, Cursor, Windsurf, and others. Point the client at your Writ MCP URL and authenticate with a wt_ key (or a csk_ consumer key for downstream callers).
Is it allowed to use monday.com this way?
Use Writ on your own monday.com account. Authorized automation of your own boards. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
rec ▸ ready

Give your agent monday.com tools

Build a workflow, publish it as an MCP tool, and call it from any MCP client. Get started free.