Skip to main content
StringsOSFree beta
Documentation: MCP & agentsExpand nav
Back to all docs
Documentation

Stop context switching. Let your AI agents manage translation keys directly from your editor.

Navigation

Configure secure API access and deploy IDE agents to automate your string extraction workflow. Connect AI-powered editors like Cursor or Windsurf to automatically sync keys to your StringsOS workspace.

1Workspace
2Settings
3API & Agents

Developer Experience

Stdio MCP Server

StringsOS provides a standard Model Context Protocol (MCP) server. Run it locally via npx to give your AI agents direct access to your workspace.

Contextual Search

Agents can search your StringsOS project for existing keys. Before creating a new key, the agent will verify if a translation already exists.

Dynamic Creation

When writing new UI components, your agent can automatically create the necessary translation keys in StringsOS without leaving the IDE.

Supported Agents

The MCP server works seamlessly with Cursor, Windsurf, Claude Code, and any other IDE that supports the MCP standard.

How to connect

To connect your agent, add the StringsOS MCP server to your IDE configuration (e.g., `.cursor/mcp.json`). You will need to provide your Project ID and a Personal Access Token.

`npx @stringsos/mcp-server --project-id=YOUR_ID --token=YOUR_TOKEN`

  • Cursor IDE integration
  • Windsurf integration
  • Claude Code integration

Setup

The Model Context Protocol (MCP) server allows your local IDE (like Cursor or Windsurf) to securely communicate with your StringsOS workspace. To configure it, you must generate a Personal Access Token in your account settings and copy your target Project ID. Provide these credentials as arguments when executing the StringsOS MCP server package locally.

Capabilities

Once connected, your IDE agent gains access to powerful localization tools. It can search for existing keys to avoid duplicates when building new components, retrieve the exact translation for a specific key in any target language, and programmatically create new keys and namespaces directly from the codebase without opening the StringsOS dashboard.

Next Steps

Keep agent access scoped to the project and use manual JSON export whenever you need a portable backup.

Import and export

Connect your agent and never manually copy-paste a key again.

Get started free
Book a demo

Free during beta · No credit card required