# Keys your app can use, straight from the design

> Get consistent key names from design, translations in JSON, CSV or ARB, and an MCP connector for your coding agent.

- **Export:** JSON, CSV, Flutter ARB
- **Sync:** Crowdin, both ways
- **Agents:** MCP connector with OAuth and per-project rights
- **Price:** Free during the beta

Copying text out of mockups into string files is slow and drifts out of date. Mondoword keeps one key per piece of UI text, linked to the design it appears in.

## How it works

1. **Keys follow your convention.** Each project has a naming convention, and suggested key names follow it (for example `checkout.cta.payNow`).
2. **Get the files.** **Export** JSON for web frameworks, ARB for Flutter, or CSV — or keep your existing Crowdin pipeline and sync with it.
3. **Let your agent help.** Connect Claude Code or Cursor through MCP. The agent can look up keys, create keys for new text, translate them and update your locale files — inside the rights you set.

## What the AI knows about each key

Keys linked to a Figma layer are translated with the frame, the element type and the text around them. Descriptions, the glossary and the style guide apply to every key.

## FAQ

### Can I keep using Crowdin?

Yes. Connect the Crowdin project; edits in Mondoword are pushed to Crowdin, and **Sync now** brings Crowdin changes in.

### Is there a CLI?

Not yet. Use **Export**, Crowdin, or a coding agent through MCP.

Source: https://mondoword.com/use-cases/app-developers · Updated 2026-10-22
