Twenty MCP Server

Created By
Tim Schauder10 months ago
An MCP server for integrating with Twenty CRM, providing access to Twenty's REST API through categorized tools. The available tools map the entire Twenty REST API and were generated using the openapi-mcp-generator.
Overview

What is Twenty MCP Server?

Twenty MCP Server is a server designed for integrating with Twenty CRM, providing access to Twenty's REST API through categorized tools. It allows users to interact with the entire Twenty REST API using tools that are automatically generated.

How to use Twenty MCP Server?

To use the Twenty MCP Server, configure it in an MCP client by specifying the desired categories or individual tools you want to enable. You will need your Twenty API key and the base URL of your Twenty instance.

Key features of Twenty MCP Server?

  • Integration with Twenty CRM's REST API.
  • Support for category-based and individual tool filtering.
  • Automatically generated tools using openapi-mcp-generator.

Use cases of Twenty MCP Server?

  1. Managing CRM data and contacts.
  2. Automating task and project management.
  3. Accessing and managing notes and documentation.

FAQ from Twenty MCP Server?

  • Is this server ready for production use?

No, the server is currently in development and not recommended for production use.

  • How do I filter tools?

You can filter tools by categories or select specific tools when configuring the MCP client.

  • What is required to run the server?

You need to provide your Twenty API key and the base URL of your Twenty instance.

Server Config

{
  "mcpServers": {
    "twenty": {
      "command": "node",
      "args": [
        "/path/to/twenty-mcp-server/build/index.js",
        "--category=crm,tasks"
      ],
      "env": {
        "TWENTY_BASE_URL": "https://your-twenty-instance.com/rest",
        "TWENTY_API_KEY": "your-api-key"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
Tim Schauder
Star
-
Language
-
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)

2 days ago