Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-create-board

Create a new Monday.com board by specifying its name and kind (public, private, or shareable). Simplifies board setup for streamlined project management.

Instructions

Create a new Monday.com board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_kindNoKind of the Monday.com board to create (public, private, shareable). Default is public.
board_nameYesName of the Monday.com board to create

Implementation Reference

  • Core handler function that executes the Monday.com board creation using the MondayClient API, including validation of board kind and returning the new board ID.
    async def handle_monday_create_board(
        monday_client: MondayClient, board_name: str, board_kind: str = "public"
    ) -> list[types.TextContent]:
        """
        Create a new Monday.com board.
    
        Args:
            monday_client (MondayClient): The Monday.com client.
            board_name (str): The name of the board.
            board_kind (str): The kind of board to create. Must be one of "public" or "private". Defaults to "public".
        """
        actual_board_kind = BoardKind(board_kind)
        board = monday_client.boards.create_board(
            board_name=board_name, board_kind=actual_board_kind
        )
        return [
            types.TextContent(
                type="text",
                text=f"Created monday board {board_name} of kind {board_kind}. ID of the new board: {board['data']['create_board']['id']}",
            )
        ]
  • MCP tool registration using @mcp.tool(), defining input schema via type hints and docstring, wrapping the handler with client initialization and error handling.
    @mcp.tool()
    async def monday_create_board(boardName: str, boardKind: Optional[str] = None) -> str:
        """Create a new Monday.com board.
    
        Args:
            boardName: Name of the Monday.com board to create.
            boardKind: Kind of the Monday.com board to create (public, private, shareable). Default is public.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_create_board(
                boardName, boardKind or "public", client
            )
            return result[0].text
        except Exception as e:
            return f"Error creating board: {e}"
  • Import of the handler function from board.py into the FastMCP server module.
    from mcp_server_monday.board import (
        handle_monday_create_board,
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write/mutation operation, it doesn't specify permissions needed, whether this requires workspace access, what happens on duplicate board names, or any rate limits. This is inadequate for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core purpose without any wasted words. It's appropriately sized and front-loaded with the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation/mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns board ID), error conditions, or behavioral constraints. Given the complexity of board creation in Monday.com, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents both parameters (board_kind and board_name). The description adds no additional parameter information beyond what's in the schema, meeting the baseline expectation when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Create') and resource ('new Monday.com board'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'monday-create-board-group' which creates board groups rather than boards, so it misses full sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'monday-list-boards' for viewing existing boards or 'monday-create-board-group' for creating board groups. There's no mention of prerequisites, context, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sakce/mcp-server-monday'

If you have feedback or need assistance with the MCP directory API, please join our Discord server