🚀 monday.com MCP

Created By
mondaycoma year ago
Enable AI agents to work reliably - giving them secure access to structured data, tools to take action, and the context needed to make smart decisions.
Overview

What is monday.com MCP?

monday.com MCP is an open framework that enables AI agents to operate reliably within real workflows by providing secure access to structured data, tools for action, and the context needed for smart decision-making.

How to use monday.com MCP?

To use monday.com MCP, create a monday.com account, generate an API token, and configure your MCP client to interact with the monday.com API. You can then ask your AI assistant questions or perform actions related to your monday.com boards.

Key features of monday.com MCP?

  • Plug-and-play server implementation for the Model Context Protocol (MCP).
  • Agent toolkit for building AI agents that interact with the monday.com API.
  • Dynamic API Tools for adaptable access to the entire monday.com API surface.

Use cases of monday.com MCP?

  1. AI Assistant for Project Management: Manage tasks and get project updates.
  2. Data Analysis & Reporting: Extract data and generate reports.
  3. Automated Workflows: Create items based on triggers and update statuses.

FAQ from monday.com MCP?

  • Can I use monday.com MCP without a monday.com account?

No, you need a monday.com account to use the MCP framework.

  • Is there a cost associated with using monday.com MCP?

The usage of monday.com MCP is free, but you may need a paid monday.com account for advanced features.

  • What programming languages are supported?

The MCP framework is built with TypeScript and is compatible with Node.js.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mondaycom
Star
6
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago