Twenty MCP Server

What is Twenty MCP Server?

An MCP server for integrating with Twenty CRM, providing access to Twenty's REST API through automatically generated, categorized tools. It is intended for local development use and has no built-in authorization, authentication, or access controls.

How to use Twenty MCP Server?

Configure the server in an MCP client by pointing to the built index.js script, setting the TWENTY_BASE_URL and TWENTY_API_KEY environment variables, and optionally passing --category or --tools arguments to filter which tools are enabled. If neither argument is provided, all categories are enabled by default.

Key features of Twenty MCP Server

• Category-based tool filtering reduces context window usage.
• Individual tool selection for precise control over enabled tools.
• Covers all Twenty REST API endpoints via categorized tools.
• Supports categories such as CRM, tasks, notes, and calendar.
• Default behavior enables all categories when no filters are set.
• Configuration supports combining categories and specific tools.

Use cases of Twenty MCP Server

• Manage contacts, companies, and people in a Twenty CRM instance.
• Create and update tasks and projects through natural language.
• Access notes, attachments, and calendar events from Twenty.
• Automate workflow or system operations via MCP client conversations.
• Filter tools to only expose CRM and tasks for focused interactions.

FAQ from Twenty MCP Server

What does Twenty MCP Server do that alternatives don't?

The README does not compare the server to alternatives. It describes the server as a tool that maps the entire Twenty REST API, generated automatically from the OpenAPI specification.

What runtime or dependencies are required?

The server is run via Node.js using the command node /path/to/twenty-mcp-server/build/index.js. No other runtime dependencies are mentioned.

Where does data live and how is it secured?

Data lives in the user's Twenty CRM instance. The server itself has no built-in authorization, authentication, or access controls; it relies on the user's API key provided via the TWENTY_API_KEY environment variable.

Is this server recommended for production use?

No. The README explicitly cautions that this is a development version and is not recommended for production use. Using it in production is at the user's own risk.

What transport or authentication method does it use?

The server connects to a Twenty CRM REST API using an API key and base URL passed as environment variables (TWENTY_API_KEY and TWENTY_BASE_URL). No other transport or authentication method is described.