Index of every page on this site: llms.txt
All skills
twentyhq avatar

/use-twenty-mcp

@6b993c2
by Twentytwentyhq/twenty61k stars
10,139
Run it yourself

Use when the user wants the agent 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.

Use this Skill: https://skilld.dev/gh/twentyhq/twenty/use-twenty-mcp

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈74 tokens for metadata: the name and description. ≈694 when used: this file. ≈56 more on demand in 1 file.

Description uses 3.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈296 characters, or 3.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

When To Use

Pick this skill when the user wants to read from or inspect a running Twenty workspace — not change app code. Representative triggers:

  • "list all my companies / people / opportunities in Twenty"
  • "show me the records I created this week"
  • "what's in my Twenty workspace"
  • "connect my agent to my Twenty workspace"
  • "set up Twenty MCP for myworkspace.twenty.com"
  • "query the CRM for X"
  • "summarize my pipeline from Twenty"
  • "show me the fields on the company object"

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).

What It Is

Twenty MCP connects the agent to an existing Twenty workspace so it 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 the agent 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.

Setup

Use ../../references/use-twenty-mcp/setup.md for workspace URL normalization, MCP server configuration, OAuth guardrails, and setup troubleshooting.

Retrieval

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.

Output Contract

Before the final answer for retrieved workspace records:

  • If the tool output includes recordReferences, the first record-name column or record heading MUST link each display name back to Twenty.
  • Build links as {workspaceOrigin}/object/{objectNameSingular}/{recordId} using the selected workspace origin and the returned recordReferences.
  • If the workspace origin is not known, resolve it from the selected MCP server URL when possible. If it still cannot be resolved, state that direct record links need the workspace URL instead of inventing a host.
  • Never show unlinked record names in a record table when recordReferences and the workspace origin are available.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill allows the agent to connect to and retrieve data from Twenty CRM workspaces. It presents a standard surface for indirect prompt injection where data managed in the CRM could potentially influence the agent's behavior.

  • Socket1mo

    1 alert: gptAnomaly

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at 6b993c2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 hours ago.

Activeupdated 2 months ago

README badge

README badge for twentyhq/twenty/use-twenty-mcp