twentyhq/twenty

Selection

Select when

• You need a customizable CRM rather than a fixed sales application.
• You want CRM objects, fields, views, workflows, and logic represented in application code.
• You want official Claude-compatible skills for Twenty app development.
• You need an MCP route from an agent to a specific Twenty workspace.
• You prefer cloud hosting or documented Docker Compose self-hosting.
• You need a TypeScript SDK and generated typed client for CRM extensions.
• You want a React component library aligned with the Twenty product.
• You need a Twenty-integrated macOS meeting-recording development path.
• You want one monorepo containing product, SDK, UI, documentation, tests, skills, and desktop code.

Boundaries

Avoid when

• You only need a small generic Claude Code enhancement.
• You need a Claude Code runtime hook, interceptor, or subagent orchestrator.
• You need a CRM-independent MCP data source.
• You require a stable Twenty UI API because the library is explicitly alpha.
• You require a signed and notarized desktop recording release.
• You require Windows or Linux desktop recording from the supplied companion.
• You cannot operate Docker for the scaffolded local-server workflow.
• You cannot permit an agent to access authenticated CRM records.
• You need independently verified security or privacy assurances.
• You require a simple single-package codebase rather than a large monorepo.

Strengths

Capabilities

Risk profile

Risks and limitations

• Uncertainty: only selected README files were supplied, so core CRM code, skill bodies, MCP implementation, manifests, tests, CI, authorization, and sandboxing were not directly inspected.
• Uncertainty: supplied metadata and companion verification dates extend into 2026, so recency, release state, adoption counts, and recorded validation cannot be independently reconciled.
• Uncertainty: the source skills on main are not directly installable through the skills CLI; installation depends on a generated agent-skills branch whose current publication state was not supplied.
• Uncertainty: no Claude Code version matrix or supplied integration-test result establishes host compatibility across releases.
• The repository metadata reports no asserted SPDX license, while supplied package documentation states AGPL-3.0 for documentation and MIT for twenty-ui; complete directory-level licensing was not established.
• The four app-development skills do not require MCP, but workspace record access requires user-specific MCP configuration and authentication.
• Agent access to a workspace can expose sensitive CRM records according to the permissions and behavior of the configured endpoint.
• twenty-ui is explicitly alpha, requires React 19, and may change APIs or behavior between releases.
• The companion is limited to Apple Silicon macOS 14.2 or newer in the supplied file and lacks signing, notarization, update delivery, and complete provider validation.
• Desktop recording requires internet access, permissions, a separately installed backend integration, Recall configuration, and disclosure to participants.
• The Kubernetes, Podman, raw-manifest, and Terraform deployment materials are stated to be community-maintained rather than maintained by the core team.
• No independent security audit, privacy assessment, Claude integration benchmark, or comprehensive production-readiness evaluation was supplied.

First-party files describe user-local workspace URLs and credentials, OAuth-capable MCP access, and SDK credentials stored under ~/.twenty/config.json. The macOS companion architecture keeps OAuth tokens and Recall upload tokens out of the renderer, uses validated IPC, PKCE, Electron safeStorage backed by macOS Keychain, and server-held Recall API credentials. These claims were not verified against implementation. Installing skills injects repository-authored guidance into the coding agent, and enabling workspace MCP gives the agent a tool surface over authenticated CRM data. Self-hosters remain responsible for secrets, deployment hardening, dependencies, network boundaries, and access control.