# Manage keys and translations from your AI chat

> Connect Mondoword to the AI assistant you already use. Ask it to find missing translations, add keys for a new screen or tidy up your glossary — inside the rights you set per project.

- **Tested with:** Claude.ai and Claude Code
- **Other clients:** MCP clients that support remote servers with OAuth
- **Sign-in:** OAuth with your Google account, no API keys
- **Rights:** View, edit or delete, per project
- **Price:** Free during the beta

You already ask an AI assistant to write, check and plan. With the Mondoword MCP connector it can also work on your translation keys: search them, add new ones, translate them with your glossary and tone, and record what needs a second look. It acts as you, and only where you allow it.

## How it works

1. **Turn on agent access.** In the Figma plugin, open the menu › **Agent access** and pick what an agent may do in this project: **View**, **Edit** or **Edit & delete**. Copy the **MCP URL** from the same panel.
2. **Add the connector.** In Claude.ai, open Settings › Connectors › Add custom connector and paste the MCP URL. In Claude Code, run `claude mcp add --transport http mondoword <MCP URL>`.
3. **Sign in once.** The first time the assistant connects, a browser window asks you to sign in with the Google account you use in the plugin.
4. **Ask in plain words.** The assistant reads the project guide, then searches, edits or translates. Every change is shown as a preview first: you see the exact list before anything is saved.
5. **Check the result in Figma.** New translations arrive as AI drafts. Preview them on the real screens in the plugin and accept them there.

## A prompt to start with

```
In my Mondoword project "Acme Money":
1. Read the project guide and the glossary.
2. List the keys in checkout.* that have no German translation.
3. Translate them into German and show me a preview before saving.
   Keep "Acme Pay" untranslated.
```

Other things to ask:

- "Which languages in this project are least complete, and which keys are missing?"
- "Add keys for the new onboarding screen: title, body and two buttons. Use our naming convention."
- "Check the French translations against the glossary and add an anomaly for each one that breaks it."

## What works today

- **Claude.ai and Claude Code** are tested end to end, including sign-in, previews and confirmed deletes.
- **ChatGPT and other assistants:** the connector follows the MCP standard with OAuth, so clients that support remote MCP servers with OAuth should work. We have not tested them yet.
- **Rights are per project.** An assistant can edit one project while another stays view-only or off.
- **Deletes and unlinking need your confirmation.** The service returns a confirmation code, so the assistant has to ask you before it can finish.
- **No images.** The assistant gets text, key names and linked layers, never pictures of your designs.

## FAQ

### Can the assistant change things I did not ask for?

Every change is shown as a preview before it is saved, deletes need your OK in the chat, and the assistant can only use the capabilities you turned on for that project. If it asks for something you did not allow, the call is refused with a note on where to turn it on.

### Do I need Figma?

To turn on agent access, yes: it lives in the Figma plugin today. After that, the assistant can create, translate and review keys without opening a design file.

Source: https://mondoword.com/use-cases/claude-and-chatgpt · Updated 2026-10-30
