Using StringPush with AI assistants

AI coding assistants can set up StringPush faster when they read the same docs a human would — and when you connect StringPush MCP servers. You never need to clone the StringPush repository. Install the local setup MCP from npm and connect to the hosted docs MCP over HTTPS.

Quick start

Give your assistant this instruction before asking it to change your app:

Use the StringPush docs at https://docs.platform.stringpush.com/llms.txt.
Follow the Getting started, Verify a browser origin, and framework integration guides.
Do not guess API endpoints. Do not commit secrets. Ask before writing .env files.

If the assistant supports larger context, use:

Read https://docs.platform.stringpush.com/llms-full.txt, then add StringPush SDK setup to this app.
Use staging first and tell me exactly which admin values I need to copy.

Recommended setup flow

1. Sign in to admin.
2. Open Settings → AI setup and create a short-lived setup token for the local MCP session.
3. Create a project and application (or use setup MCP — see below).
4. Add your staging and local browser origins.
5. Verify non-localhost origins.
6. Create a test key, publish staging, and install @stringpush/sdk@0.7.0 (latest on npm).
7. Run your app locally and confirm the SDK loads staging translations.

Your assistant should use:

• Getting started
• Verify a browser origin
• Integration hub
• Staging overlay

Choose your assistant

StringPush provides two MCP paths:

MCP	Where it runs	Credentials	Install
Docs MCP	Hosted by StringPush (AWS)	None — read-only public docs	Remote URL via mcp-remote
Setup MCP	Your machine (stdio)	Short-lived STRINGPUSH_SETUP_TOKEN	npx @stringpush/setup-mcp

Docs MCP (read-only)

Production endpoint: https://mcp.docs.platform.stringpush.com/mcp

Cursor — ~/.cursor/mcp.json or project .cursor/mcp.json:

{
  "mcpServers": {
    "stringpush-docs": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.docs.platform.stringpush.com/mcp"]
    }
  }
}

Claude Desktop / Claude Code — same JSON shape in your Claude MCP config file:

{
  "mcpServers": {
    "stringpush-docs": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.docs.platform.stringpush.com/mcp"]
    }
  }
}

Generic — any MCP client that supports remote servers:

npx mcp-remote https://mcp.docs.platform.stringpush.com/mcp

Then ask:

Use the stringpush-docs MCP. Fetch /getting-started and /integration/verify-domain, then help me add StringPush to this app.

Setup MCP (local writes)

Setup MCP runs on your machine so setup tokens and one-time runtime keys never pass through a hosted MCP service. Install from npm — do not clone the StringPush monorepo.

Create a token in Settings → AI setup (shown once, expires within one hour).

Cursor:

{
  "mcpServers": {
    "stringpush-setup": {
      "command": "npx",
      "args": ["-y", "@stringpush/setup-mcp"],
      "env": {
        "STRINGPUSH_API_BASE": "https://api.platform.stringpush.com",
        "STRINGPUSH_SETUP_TOKEN": "<short-lived setup token>"
      }
    }
  }
}

Claude Desktop / Claude Code — same block under mcpServers in your Claude config.

Variable	Required	Purpose
STRINGPUSH_SETUP_TOKEN	yes	Token from Settings → AI setup
STRINGPUSH_API_BASE	no	Defaults to https://api.platform.stringpush.com

Then ask:

Use the stringpush-setup MCP to list projects, create or reuse a setup project, create an application with localhost and staging origins, seed common.greeting, publish staging, and validate runtime ping.
Ask before any tool call that needs confirm=true. Never write .env files unless I explicitly approve.

Prompt examples

Plain browser app

Use the StringPush docs from https://docs.platform.stringpush.com/llms.txt.
Find this app's browser entry point, install @stringpush/sdk, initialize it with environment variables, and replace one visible string with t("common.greeting").
Do not hardcode runtime API keys. Show me the .env.local keys I need to add.

Vite + React

Use the StringPush docs from https://docs.platform.stringpush.com/llms.txt.
Install @stringpush/react and @stringpush/sdk, initialize StringPush in the browser entry point, and replace one visible string with useTranslation().t("common.greeting").
Use staging first. Do not commit runtime keys or .env.local.

Next.js

Use the StringPush Next.js and plain SDK docs from https://docs.platform.stringpush.com/llms.txt.
Add client-side StringPush initialization only where browser APIs are available.
Keep runtime keys in NEXT_PUBLIC_* environment variables and start with staging.

Vue

Use the StringPush Vue docs from https://docs.platform.stringpush.com/llms.txt.
Install @stringpush/vue and @stringpush/sdk, register the translation plugin in the Vue app entry point, and replace one visible string with the StringPush translation helper.
Keep runtime keys in local environment variables and do not commit them.

Angular

Use the StringPush Angular docs from https://docs.platform.stringpush.com/llms.txt.
Install @stringpush/angular and @stringpush/sdk, add the provider at app bootstrap, and replace one visible template string with the translate pipe.
Use staging and wait for me to provide applicationId and runtime API key values.

Domain verification

Use https://docs.platform.stringpush.com/integration/verify-domain.md.
Explain which DNS TXT or HTTP file I need to add for my staging origin, then wait for me before checking verification.

Rails / Ruby SSR

Read https://docs.platform.stringpush.com/integration/server-http-client
and https://docs.platform.stringpush.com/concepts/manifest-and-bundles.
Implement a minimal read-only StringPush runtime for Rails: manifest + bundle fetch,
Authorization and Origin headers, and t(key) with simple {name} interpolation.
Cache per locale. Do not commit runtime API keys.

Laravel / PHP SSR

Use the StringPush server HTTP client docs from https://docs.platform.stringpush.com/llms.txt.
Add a Laravel service that loads manifest and bundle JSON for staging,
sends Origin matching our public site URL, and exposes t("key") in Blade.
Ask me for applicationId, apiBaseUrl, and runtime key before writing .env.

Phoenix / Elixir SSR

Read /integration/server-http-client and /concepts/manifest-and-bundles via stringpush-docs MCP.
Create a Phoenix context module that fetches manifest + bundle (Req or Finch),
passes Origin for allowlist auth, and returns translated assigns for HEEx templates.
For Gettext-native apps, mention Git sync as an alternative.

Django / Python SSR

Follow https://docs.platform.stringpush.com/integration/server-http-client.
Add a small Python module for Django views: GET manifest then bundle,
Bearer runtime key + Origin header, flat JSON catalog, and t(key, **vars).
Use environment variables for secrets; do not commit them.

Secret handling

• Never paste runtime API keys into public chat logs.
• Do not ask the assistant to commit .env.local.
• Create setup tokens from Settings → AI setup and copy them once; StringPush stores only a hash.
• Save the runtime API key when the application is created; it is shown once.
• Use staging first. Production publish and promotion are not part of the AI setup flow.
• Use one setup token per user/session. Do not share setup MCP configs across teammates.