AI assistants (MCP)
Edit app content with Claude, Cursor and other AI assistants
Connect Claude, Cursor or VS Code to your CMSCure projects with the MCP server. Ask the assistant to fix copy, translate a screen or update colors, then publish.
The problem
Large content jobs, like rewriting every string on a screen, adding a new language or changing a color palette, used to mean exporting a file, editing it somewhere else and importing it back. The CMSCure MCP server lets an AI assistant read and edit your project directly, so you describe the change and review it instead of moving files around.
Who it is for
- Developers who already use Claude Code, Cursor or VS Code and want to edit app content from there
- Teams that need to translate or rewrite many keys at once
- Designers and developers who want to update a whole color palette in one request
- Anyone who wants AI help with content but still wants to review changes before they go live
How it works
- 1
Create an access token
In the CMSCure dashboard, open Settings, Access tokens and create a token. Choose read only or read and write, limit it to some projects if you like, and set an expiry. The token is shown once.
- 2
Add the MCP server to your assistant
Add @cmscure/mcp to Claude Code, Claude Desktop, Cursor, VS Code or any MCP client. It runs with npx and reads your token from the CMSCURE_TOKEN environment variable.
- 3
Ask for the change
Ask in plain language, for example: fix the typos on the checkout screen, translate the home screen into French, or make the primary colors darker. The assistant reads your keys and writes the changes as drafts.
- 4
Review and publish
Check the pending changes in the dashboard or ask the assistant to list them. Nothing reaches your apps until you publish, and the publish tool asks for an explicit confirmation.
What the assistant can do
The MCP server has 15 tools. It can list your projects, read text by screen, language, key or search term, add or change text, read and update colors, list unpublished changes, publish, and on the Pro plan list versions and roll back a screen or your colors.
For big jobs it can export a screen to a local JSON file, let the assistant edit the file, and import it back with a dry run first. Large imports are sent in chunks.
Drafts first, publish on purpose
Every edit made through the MCP server is saved as a draft, exactly like an edit in the dashboard. Your apps keep showing the last published content until someone publishes, so you can review what the assistant changed and revert single keys if needed.
Token control
Access tokens are stored hashed and can be revoked at any time in Settings. A token can be read only, limited to chosen projects and set to expire. Viewer, Editor and Admin roles still apply, so a token can never do more than its owner can.
What stays in the dashboard
Screens and languages are created in the dashboard, not through the MCP server, so an assistant cannot add a screen or language by mistake. Images and data stores are managed in the dashboard for now.
Management API
The MCP server is built on the CMSCure management API at app.cmscure.com/api/v1. You can call the same API from your own scripts or CI with a Bearer access token.
Set it up
The documentation covers installation and code for every SDK.
Frequently asked questions
Which AI assistants work with CMSCure?
Any client that supports the Model Context Protocol over stdio, including Claude Code, Claude Desktop, Cursor and VS Code. The server is the npm package @cmscure/mcp.
Can the assistant publish without me?
Edits are saved as drafts. The publish tool only runs when it is called with an explicit confirmation, and you can give the assistant a read only token if you only want it to read content.
Is my content sent to a third party?
The MCP server runs on your own computer and talks to the CMSCure API with your token. The content it reads is shared with the AI assistant you connect it to, under that assistant's own terms.
Do I need a paid plan?
Reading and editing work on any active project, including the free first month. Version history and rollback need the Pro plan, as in the dashboard.
Guides
More features
Ready to stop waiting on UI releases?
Read the docs to see how fast you can integrate, or start building with CMSCure today.