Is Integrations free?

Yes, Integrations is free to use.

How do I install Integrations?

Integrations is a local plugin. Install it using npm package: @translatize/mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Integrations safe to use?

Yes. Integrations passed MCP Marketplace's automated security scan with a score of 9.7/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Integrations need?

Integrations requires the following credentials or environment variables: TRANSLATIZE_API_TOKEN, TRANSLATIZE_API_URL, TRANSLATIZE_APP_URL. You can find setup instructions on the server detail page.

What AI apps work with Integrations?

Integrations uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Integrations MCP Server

by Translatize

Developer ToolsLow Risk9.7MCP RegistryLocal

Free

Server data from the Official MCP Registry

Read, search, edit and branch Translatize translation labels and fill missing translations.

About

Read, search, edit and branch Translatize translation labels and fill missing translations.

Security Report

9.7

Low Risk9.7Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

8 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Translatize integration API token (an "mcni_..." string), bound to one project and branch. Create it under Project Settings -> Integrations at https://app.translatize.com.Required

Environment variable: TRANSLATIZE_API_TOKEN

API base URL including the /v1 segment. Defaults to https://api.translatize.com/v1.Optional

Environment variable: TRANSLATIZE_API_URL

Web-app base URL used to build review links. Defaults to https://app.translatize.com.Optional

Environment variable: TRANSLATIZE_APP_URL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "com-translatize-mcp": {
      "env": {
        "TRANSLATIZE_API_URL": "your-translatize-api-url-here",
        "TRANSLATIZE_APP_URL": "your-translatize-app-url-here",
        "TRANSLATIZE_API_TOKEN": "your-translatize-api-token-here"
      },
      "args": [
        "-y",
        "@translatize/mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Translatize integrations

Client-side tooling for the Translatize integration API (the machine-token API authenticated with Authorization: Bearer mcni_...). This is an npm workspace root that is intentionally separate from the apps in the repo – it has the only package.json with workspaces, and the repo root stays package.json-free.

Packages

Package	Directory	Status	What it is
`@translatize/core`	`core/`	available	Zero-dependency TypeScript SDK for the integration API (client + flatten/unflatten helpers). The shared foundation everything else builds on.
`@translatize/cli`	`cli/`	available	Command-line tool (`translatize init/pull/push/status`) built on `@translatize/core`. Syncs translations from CI with git-like branching.
`@translatize/mcp`	`mcp/`	available	Model Context Protocol server exposing the API to AI agents (Claude Code, Cursor, ...) over stdio, built on `@translatize/core`.

CI templates

Two ready-to-use CI integrations complement the packages. They shell out to the @translatize/cli (npx @translatize/cli ...) rather than being npm packages, so you consume them as workflow/pipeline config, not via npm install:

Template	Home	What it is
GitHub Action	github.com/Translatize/sync-action	Composite action (`translatize/sync-action`) wrapping the CLI's `pull`/`push`/`status` for GitHub workflows.
GitLab CI	gitlab.com/translatize/gitlab	CI/CD Catalog component (`templates/translatize.yml`) plus copy-paste `.gitlab-ci.yml` jobs.

Development

cd integrations
npm install        # installs every workspace and hoists dev deps
npm run build      # builds each workspace that defines a build script
npm test           # runs each workspace's test suite

Requires Node.js >= 18.17 (native fetch, node:test).

Publishing

The @translatize/core, @translatize/cli, and @translatize/mcp packages are published to npm under the @translatize scope. Publishing is manual – nothing here publishes automatically. To cut a release, build first, then npm publish --access public from the individual package directory (or npm publish --workspaces).

Reviews

No reviews yet

Be the first to review this server!

More Developer Tools MCP Servers

Fetch

Free

by Modelcontextprotocol · Developer Tools

Web content fetching and conversion for efficient LLM usage

Toleno

Free

by Toleno · Developer Tools

Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.

mcp-creator-python

Free

by mcp-marketplace · Developer Tools

Create, build, and publish Python MCP servers to PyPI — conversationally.

Integrations MCP Server

About

Security Report

Findings (1)

Permissions Required

What You'll Need

How to Install

Documentation

Translatize integrations

Packages

CI templates

Development

Publishing

Reviews

No reviews yet

More Developer Tools MCP Servers

Fetch

Toleno

mcp-creator-python

MarkItDown

MCP Marketplace

FinAgent