twentycrm-graphql-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TWENTY_GQL_URL | No | Your Twenty instance's GraphQL endpoint. For cloud-hosted, it's https://[your-org].twenty.com/graphql. For self-hosted, it's https://[your-domain]/graphql. | |
| TWENTY_API_TOKEN | Yes | Your Twenty API token (Settings > API & Webhooks) |
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 |
|---|---|
| inspect_schemaA | Lists all available objects and fields, including CUSTOM fields created in your workspace. |
| execute_graphqlB | Run any raw GraphQL query or mutation against Twenty. |
| execute_metadataA | Run any raw GraphQL query or mutation against the Twenty Metadata API (schema management: custom objects, fields, relations). |
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 3 tools
Each tool has a clear, distinct role: schema introspection, runtime data queries/mutations, and metadata schema management. Even though execute_graphql could theoretically run introspection, the dedicated inspect_schema tool removes ambiguity.
All tool names follow a consistent snake_case verb_noun pattern: inspect_schema, execute_graphql, execute_metadata. The repeated execute prefix for the two raw query tools also reinforces their similarity without causing confusion.
Three tools is appropriately minimal for a GraphQL gateway-style MCP server. Each tool covers a distinct need (schema discovery, data access, metadata management) and none feels redundant or extraneous.
The combination of raw GraphQL execution for both the standard API and metadata API covers the full CRUD/lifecycle surface of a Twenty CRM workspace, while inspect_schema supports discovery. There are no obvious dead ends because arbitrary queries and mutations can fill any domain-specific gap.