Skip to main content
The server runs remotely at https://api.dittowords.com/v2/mcp, authenticates with your Ditto account, and gives an agent the operations a person has in the Ditto app. The goal is parity with the Ditto app. Anything you can do in the UI, you can do through the MCP server, and new capabilities ship to both. To connect a client, see Setup. Every tool, with its parameters and constraints, is defined on the Tools page. Prompts for the tasks below are on Agent instructions.

​
What teams use it for

​
Bring product text into Ditto

  • Spin up a new Ditto project from an AI prototype. The agent reads the copy in a prototype, creates a project, and adds each string as a text item with a developer ID and a status. Designers and writers refine the text in Ditto while the developer keeps building against the IDs.
  • Bulk-create text items. From a design, a spreadsheet, or a list in chat, the agent checks each string against what already exists, reuses the matches, and creates the rest with developer IDs, tags, and statuses in one call.
  • Replace hardcoded strings. After a scan, the agent swaps string literals in code for the developer IDs of the library components Ditto created from them.

​
Write on-brand copy

  • Generate UI with compliant text. Before writing copy for a new screen, the agent fetches your style guide rules and searches for text that already says it, then checks what it wrote against the rules.
  • Brainstorm with full context. Asked for options, the agent proposes copy informed by the words your library already uses and the rules your team has agreed on, rather than starting from a blank page.
  • Review a diff before committing. The agent audits the user-facing strings in a change for rule violations and near-duplicates of existing text, and reports them before they ship.

​
Keep the workspace consistent

  • Run a global search for near-duplicates. The agent finds the variations of a phrase across the workspace (“Log in”, “Log In”, “Sign in”), consolidates them onto one approved version, and adds it to the library.
  • Clean up after a style guide change. When a rule changes, the agent finds every text item that now breaks it and updates them in bulk. When a review comment reveals a pattern, it adds the rule to the style guide.
  • Reorganize your component library. The agent creates folders and moves components into them so the library follows your product’s structure.

​
Localize

  • Draft a new variant for translated copy. The agent adds the locale, translates the text following that locale’s style guide, and writes the translations to each text item for a localization manager to review.

​
Connect designs

  • Link a Figma file’s text to Ditto. The agent reads the text layers of a connected Figma file, matches them to existing text, shows you anything ambiguous, and links the layers so design and code share developer IDs. Walkthrough: Connect Figma files.

​
Scope results to your codebase

Add ditto/config.yml (or ditto/config.yaml) at the repo root listing the Ditto projects this codebase owns:
When present, get_styleguide_rules, search_ditto_text, and list_projects read it and scope their results to those projects. This is the same file the CLI’s pull command uses, so one committed file serves both; everything else it can contain is in CLI configuration.

​
Permissions and attribution

With your Ditto login, tools run with your Ditto permissions and actions are attributed to you in Ditto’s activity history. With an API key, tools run as the user who created the key.