Globalize gives you three ways to reach the same backend. They do different jobs, and most people use more than one. Here's how they fit together.
The skills — they change your code
npx skills add globalize-now/globalize-skills installs a playbook into your coding agent (Claude Code, Cursor, Codex). The agent then does the part that touches your codebase: it detects your framework, installs the right i18n library, finds your hardcoded English text, and turns it into translation keys and a source locale file. This is the only piece that edits your components.
Use the skills when your app isn't internationalized yet, or when you add new UI and want it wired up correctly.
If your agent is already connected to the MCP server, you don't have to install the skills by hand. The server exposes an install-skills prompt (a slash command in Claude Code, Cursor, Windsurf, or Codex) that installs the whole skill set in one step. From then on they auto-trigger on requests like "set up i18n" or "translate my app".
The MCP server — it manages localization and translates files
The MCP server connects an AI agent to your Globalize account. Through it, the agent can create projects, add languages, translate locale files, connect your GitHub repo, and manage your glossary and style guides. It works on locale files and project settings — it does not edit your source code.
Use the MCP when you want to drive Globalize from inside Claude, Cursor, or another agent without leaving your editor.
The CLI — the command layer underneath
The globalize CLI is the command surface the skills call for account, project, and repository setup. You rarely run it directly; the skills handle it for you. It's there if you want scripted, non-interactive control.
A typical first run
- Skills internationalize your code and produce
messages/en.json(or your framework's equivalent). - MCP or CLI creates the project, translates that file into your target languages, and connects your repo.
- From then on, every push that adds new English text triggers a translation pull request automatically.
The short version
If your question is "why won't the MCP internationalize my app?" — that's expected. The MCP manages and translates; the skills change your code. Run the skills first, then let the MCP take it from there.