メニュー
Use when the user wants Codex to connect to an existing Twenty workspace through MCP, retrieve or inspect workspace records and metadata, or present Twenty CRM data as readable Markdown with formatted dates, values, record links, and compact tables instead of raw API output.
Retrieve and present Twenty CRM records as readable summaries or tables, using the connected Twenty MCP server to discover fields, fetch relevant data, format dates and values, build record links, and avoid raw API output.
Use when the user wants to create or scaffold a new Twenty app
Use when the user wants to add or modify Twenty app entities, including objects, layouts, logic functions, and front components inside an existing Twenty app.
Use when the user wants to manage or troubleshoot tooling, remotes, sync, build, deploy, logs, CI/CD, or operational workflows for an existing Twenty app.
Use when the user wants to prepare or verify a Twenty app for npm or marketplace publication, including README/About copy, package metadata, defineApplication marketplace metadata, logos, screenshots, and public assets.
Use when turning a qualified Twenty lead — a call-summary brief plus any client braindump/docs — into an implementation design doc a partner can scope and quote from. Trigger when pointed at a lead folder (e.g. partners-experience/<LEAD>/) and asked to "draft a design doc", "translate this into Twenty terms", "scope this for a partner", or "prep the partner handoff" for a discovery-qualified prospect. Chains after twenty-lead-intro-call-summary.
| name | use-twenty-mcp |
| description | Use when the user wants Codex to connect to an existing Twenty workspace through MCP, retrieve or inspect workspace records and metadata, or present Twenty CRM data as readable Markdown with formatted dates, values, record links, and compact tables instead of raw API output. |
Pick this skill when the user wants to read from or inspect a running Twenty workspace — not change app code. Representative triggers:
myworkspace.twenty.com"Do not use this skill to scaffold an app (use create-app), to add or modify app entities (use develop-app), to operate an app (use manage-app), or to prepare marketplace assets (use publish-app).
Twenty MCP connects Codex to an existing Twenty workspace so the agent can inspect workspace data and metadata: records, objects, fields, schema, configuration, and related CRM context.
This is different from a Twenty app. Use $create-app when the user wants to scaffold a new app codebase, and $develop-app when the user wants to add app-defined features such as objects, fields, logic, layouts, or components.
Use $use-twenty-mcp when the user wants to connect Codex to an already running workspace, retrieve or inspect workspace data, inspect metadata, or troubleshoot MCP access.
Do not use MCP as the default way to customize a workspace. For example, prefer creating a new object through a Twenty app rather than directly through MCP. Use MCP for workspace customization only when the user explicitly asks to do it through MCP.
Use ../../references/use-twenty-mcp/setup.md for workspace URL normalization, MCP server configuration, OAuth guardrails, and setup troubleshooting.
Before retrieving, listing, searching, summarizing, or presenting workspace records, read ../../references/use-twenty-mcp/result-formatting.md.
Apply that reference when selecting the right Twenty MCP workspace, querying records, building record links, formatting dates and values, and presenting readable Markdown instead of raw API output.
Before the final answer for retrieved workspace records:
recordReferences, the first record-name column or record heading MUST link each display name back to Twenty.{workspaceOrigin}/object/{objectNameSingular}/{recordId} using the selected workspace origin and the returned recordReferences.recordReferences and the workspace origin are available.