Connect Frontitude to Cursor so its agent uses your team's approved copy and string keys while it writes code, instead of hardcoding new text. Add it to the repo once and everyone who works on it gets the same setup.

‍

‍

Before you start

• Sign in to Cursor with your company account.
• Pull the latest version of the repo, in case a teammate already added Frontitude.
• Make sure you can open a pull request on the repo, or line up a teammate to review your change.
• Make sure AI tools integration is turned on in your Frontitude workspace from Settings → AI.

‍

‍

Check whether your repo already has it

Open .cursor/mcp.json at the root of the repo. If it already lists frontitude, skip to Sign in.

‍

‍

Add Frontitude to the repo

1. Create .cursor/mcp.json at the repo root, or open the existing one.
2. Add the frontitude entry inside mcpServers:

{
 "mcpServers": {
   "frontitude": {
     "url": "https://mcp.frontitude.com/mcp"
   }
 }
}


3. Commit the file and open a pull request, so teammates get Frontitude when they pull. The file holds no secrets: each person signs in with their own account.

‍

Working on something outside a shared repo? Add the same entry to ~/.cursor/mcp.json in your home folder instead.

‍

‍

Sign in

1. Open Customize in Cursor's sidebar and make sure Frontitude is turned on.
2. When Cursor asks, sign in to Frontitude with your work account and approve access.

‍

Cursor asks before running each Frontitude tool. Follow your team's policy before allowing any tool to run without asking.

‍

‍

Example prompts

• Use approved copy: "Build the empty state for the projects list using the approved copy from Frontitude."
• Replace hardcoded strings: "Find hardcoded user-facing strings in this component and match them to Frontitude keys."
• Check a PR's copy: "Compare the new strings in this diff with Frontitude and flag any that don't match."
• Add new copy for review: "Add the new strings from this feature to Frontitude as drafts so our writers can review them."

‍

To sync strings into your codebase automatically, use the Frontitude Developer CLI alongside the MCP.

‍

‍

If something doesn't work

• Frontitude doesn't appear — check the JSON is valid and the file is at the repo root, then restart Cursor.
• Frontitude is blocked or turned off — your company may limit which MCP servers Cursor can use. Ask your Cursor admin to allow https://mcp.frontitude.com/mcp.
• Sign-in fails or shows the wrong workspace — sign out of any personal Frontitude account in your browser, then reconnect from Customize with your work account.
• The agent doesn't use Frontitude — mention Frontitude in your prompt, and check the server is turned on.

‍

Want the full details? Read Cursor's own guide: Model Context Protocol (MCP).

‍

Ready to try it out? See prompt samples for Frontitude MCP.