mcp -monday

This MCP server exposes a set of Monday.com focused tools that let clients interact with boards, items, updates, and documents. The included tools cover common Monday.com operations such as creating items and boards, listing boards or groups, moving items between groups, posting updates, and retrieving or manipulating documents. Clients can invoke tools like monday-create-item, monday-get-board-groups, monday-create-update, monday-list-boards, monday-list-items-in-groups, monday-list-subitems-in-items, monday-create-board, monday-create-board-group, monday-move-item-to-group, monday-delete-item, monday-archive-item, monday-get-item-updates, monday-get-docs, monday-get-doc-content, monday-create-doc, and monday-add-doc-block. To use the server, configure your environment with a Monday.com API key and the workspace name, then start the uvx-bridged server as shown in the installation notes. Once running, you can query the available tools and perform actions against your Monday.com workspace through the MCP client, subject to your API permissions in Monday.com.

Prerequisites:

• Access to a system with Python and Node tooling as needed by your environment
• Monday.com API key with appropriate permissions
• uvx (uv) installed and configured on your system

Installation steps:

1. Install the uvx tool if you haven't already. This enables running MCP servers packaged as Python/UV based projects.
   • Example (npm): npm install -g uvx (adjust per your environment)
2. Install or ensure access to the Monday MCP server package named mcp-server-monday via uvx.
   • This typically involves ensuring the package is available in your environment (e.g., via PyPI/uv index) and that your PATH includes the uvx executable.
3. Prepare environment variables for Monday.com:
   • MONDAY_API_KEY: Your Monday.com API token
   • MONDAY_WORKSPACE_NAME: The Monday.com workspace name derived from your workspace URL
4. Start the MCP server:
   • Using uvx: uvx run mcp-server-monday
   • Or if using a container/managed environment, configure the container to expose the same environment variables and run the package as shown in the examples.
5. Validate operation:
   • Connect a MCP client and list available tools, then perform a test operation such as listing boards or creating a test item to confirm connectivity.

Tips and common issues:

• Ensure MONDAY_API_KEY has the necessary permissions for the tests you run (read/write as needed).
• The MONDAY_WORKSPACE_NAME should match exactly what appears in your Monday.com workspace URL (case sensitive).
• When using Docker or uvx, ensure environment variables are properly passed to the process; some environments require explicit -e flags or docker-compose env blocks.
• Debugging MCP servers over stdio can be tricky; consider using the MCP Inspector tool to visualize requests and responses during development.
• If you encounter authentication errors, re-check API token validity and workspace scope.
• If the server fails to start, verify that the mcp-server-monday package is accessible to uvx and that the command path is correct in your environment.