Guides

Edit app text and translations with Claude or Cursor using MCP

CMSCure team, November 18, 2026

Small text fixes are quick in any dashboard. Big content jobs are not: rewriting every string on a screen, translating a whole app into a new language, or moving a color palette to a darker shade. Until now the usual way was to export a file, paste it into an AI assistant, copy the result back and import it. With the CMSCure MCP server, Claude, Cursor or VS Code can work on your project directly, and you stay in charge of what gets published.

What MCP is, in one paragraph

The Model Context Protocol (MCP) is an open standard that lets an AI assistant call tools in other systems. An MCP server describes a set of tools, such as read content or update colors, and the assistant decides when to call them while it works on your request. Claude Code, Claude Desktop, Cursor and VS Code all support MCP servers that run locally over stdio.

The CMSCure MCP server is the npm package @cmscure/mcp. It runs on your computer, talks to the CMSCure management API with your personal access token, and gives the assistant 15 tools for projects, text, colors, drafts, publishing and version history.

Why not just export and import a file?

Export and import still works, and it is still a good fit for backups and one off migrations. For everyday content work it adds steps that are easy to get wrong: picking the right screen and languages, keeping key names exactly as they were, and remembering which file is the latest.

When the assistant can read the project itself, it sees the real keys, the real languages and the current values. It writes only the keys it changes, merged per language, and every change lands as a draft you can review before anything reaches your users.

Set it up in two minutes

First, open Settings in the CMSCure dashboard, go to Access tokens and create a token. Choose read and write if the assistant should edit content. You can limit the token to some projects and set an expiry. Copy the token, it is shown only once.

Second, add the server to your assistant. In Claude Code, one command is enough. In Cursor, VS Code or Claude Desktop, add the same command to the MCP config file with the token in the CMSCURE_TOKEN environment variable. The docs page has the exact config for each client.

bash
claude mcp add cmscure \
  --env CMSCURE_TOKEN=cmsc_pat_your_token \
  -- npx -y @cmscure/mcp

Example 1: rewrite a screen

Ask: "In my Shop app, rewrite the checkout screen text in English so it is shorter and friendlier, keep the meaning, and do not touch the keys." The assistant lists your projects, reads the checkout screen in English, proposes new values and saves them with update_content.

You can ask it to run a dry run first. The dry run returns what would change without saving anything, which is a good habit for larger edits.

Example 2: translate a whole screen or app

Ask: "Translate the home and onboarding screens into French and German. Keep placeholders like {name} unchanged." The assistant reads the English values and writes the French and German values for the same keys.

The languages must already exist in the project. Languages and screens are added in the dashboard, so an assistant cannot create them by accident. For very large screens the assistant can export the content to a local JSON file, edit the file, and import it back; big imports are sent in chunks.

  • Add the target language in the dashboard first
  • Ask the assistant to keep placeholders and formatting as they are
  • Review a few keys per language before you publish

Example 3: update colors

Ask: "Make every primary and accent color about 10 percent darker and keep the background colors as they are." The assistant reads your colors with get_colors and writes new #RRGGBB values with update_colors. Like text, color changes are drafts until you publish.

Review, then publish

Every change made through MCP shows up in the dashboard as an unpublished change, next to edits made by your team. You can revert single keys there, or ask the assistant to list pending changes with get_pending_changes.

Publishing is a separate step. The publish tool only runs when it is called with an explicit confirmation, so a vague request will not push content to your apps. When you do publish, connected apps get the update over WebSocket, the same as a publish from the dashboard. On the Pro plan you can also list versions and roll back a screen or your colors through the assistant.

Keeping it safe

Access tokens are stored hashed and can be revoked any time in Settings. Use a read only token when the assistant only needs to read, and a project limited token when it should only touch one app. Team roles still apply, so a token can never do more than its owner.

The MCP server runs on your machine. Content the assistant reads is sent to the AI provider you use, under that provider's terms, so treat it like any other text you paste into an assistant.

What the MCP server does not do yet

It covers text, colors, drafts, publishing and version history. Images and data stores are still managed in the dashboard, and screens and languages are created there too. The server runs locally with npx; a hosted remote endpoint is not available yet.

Frequently asked questions

Which assistants can use the CMSCure MCP server?

Any MCP client that runs local servers over stdio, including Claude Code, Claude Desktop, Cursor and VS Code.

Will the assistant change my live app on its own?

No. Edits are saved as drafts. Your apps only change after a publish, and the publish tool needs an explicit confirmation.

Can I use the API without an AI assistant?

Yes. The MCP server is built on the management API at app.cmscure.com/api/v1, which you can call from scripts or CI with a Bearer access token.

Does it work on the free first month?

Yes. Reading and editing work on any project with an active plan, including the free first month. Version history and rollback need the Pro plan.

Related features

Related guides

Ready to stop waiting on UI releases?

Read the docs to see how fast you can integrate, or start building with CMSCure today.

Edit App Translations with Claude and MCP | CMSCure