monday-graphql-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MONDAY_API_KEY | No | Your monday.com API key. Required for some tools like get_schema and run_query, but the server can run without it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| column_value_formatA | Returns the exact read and write JSON format for any monday.com column type. No API key required. Use this whenever you need to know how to read or write a column value. |
| explain_errorA | Explains a monday.com API error response in plain language and suggests a fix. Paste the error JSON or message. No API key required. |
| scaffoldA | Generates ready-to-use boilerplate code for monday.com integrations and apps. No API key required. |
| get_schemaA | Fetches the live monday.com GraphQL schema and returns type definitions, available queries, and mutations. Requires a monday.com API key. |
| validate_queryA | Validates a monday.com GraphQL query: checks syntax, estimates complexity, and flags common pitfalls. Optionally validates against the live schema when an API key is provided. |
| run_queryB | Executes a GraphQL query or mutation against the monday.com API and returns the result. Requires a monday.com API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct use case: schema retrieval, query execution, query validation, column formatting, error explanation, and scaffolding. There is minimal conceptual overlap between them, and the descriptions make the boundaries clear.
Most tools use a clear verb_noun pattern (get_schema, validate_query, run_query, explain_error, scaffold), but column_value_format deviates by being a noun phrase rather than an action-oriented name. This is a minor inconsistency and does not prevent readability.
Six tools is a well-scoped set. Each tool addresses a distinct part of the monday.com GraphQL development workflow, and none feel redundant or unnecessary.
The set covers the full developer workflow: retrieving schema, validating queries, executing queries, understanding column value formats, troubleshooting errors, and generating boilerplate code. Since run_query handles arbitrary GraphQL operations, there are no obvious dead ends.