twenty

Twenty MCP Server exposes Twenty CRM REST API capabilities as a collection of tools that can be selectively enabled. Tools are organized by categories (e.g., crm, tasks, notes) or can be filtered to specific operations, giving you fine-grained control over which endpoints are exposed to your MCP client. When configured, clients can query the MCP server to discover available tools and then invoke them through standardized calls, enabling automation and integration with other systems. The server pulls tool definitions from the Twenty OpenAPI schema and mirrors those operations as MCP tools, allowing you to work with familiar Twenty REST endpoints via the MCP interface.

To use the server, you typically start it with Node and point your MCP client to the built index.js entry point. You can limit exposure by supplying either --category arguments (to enable entire groups of tools) or --tools arguments (to enable individual operations). For example, enabling crm and tasks categories will surface all tools under those areas, while listing specific tool names (like findManyCompanies or createOneNote) will restrict the set precisely to what you need. This selective exposure helps reduce context window usage, lower costs, and improve performance in client applications.

Prerequisites:

• Node.js and npm installed
• Access to a Twenty CRM instance and API key (for production use you’ll provide your own TWENTY_BASE_URL and TWENTY_API_KEY)

Install and build the server:

# Clone the repository
git clone https://github.com/your-org/twenty-mcp-server.git
cd twenty-mcp-server

# Install dependencies
npm install

# Build the server (generates build/index.js or equivalent)
npm run build

Run the server (example):

# Start the MCP server (adjust the path to your built index.js)
node /path/to/twenty-mcp-server/build/index.js

Configure your MCP client to connect to the server using the provided mcp_config example, and provide the necessary environment variables (TWENTY_BASE_URL and TWENTY_API_KEY) for authentication with Twenty.

Environment variables and configuration:

• TWENTY_BASE_URL should point to your Twenty REST API base URL (e.g., https://your-twenty-instance.com/rest).
• TWENTY_API_KEY should be your valid Twenty API key.

Performance tips:

• Use category-based filtering or precise tool lists to minimize the number of tools loaded and improve responsiveness.
• The server is labeled as a development version; avoid using it in production without proper testing and security hardening.

Common issues:

• If tools fail to load, verify that the TWENTY_BASE_URL is reachable from the server and that the API key has the necessary permissions.
• Ensure npm run build completes successfully before starting the server, as missing build artifacts will cause startup failures.