# Phrase MCP [Health: Active]

**Category:** 🌎 Translation Services  
**Repository:** https://developers.phrase.com/en/mcp-server  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/phrase-mcp

## Description
Phrase MCP server: language intelligence platform for translation, terminology, and quality.

## Tools
Capabilities this server exposes over MCP:

- **search_phrase_developer_hub** — Search across the Phrase Developer Hub knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Phrase Developer Hub, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).
- **query_docs_filesystem_phrase_developer_hub** — Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Phrase Developer Hub documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.

This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`.

**Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered.

**Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.

Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage.

Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call.

Examples (replace the placeholder paths with real ones from `tree` or search):
- `tree / -L 2` — see the top-level directory layout
- `rg -il "rate limit" /` — find all files mentioning "rate limit"
- `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit
- `head -80 /some/page.mdx` — read the top 80 lines of a specific page
- `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call
- `cat /some/page.mdx` — read a full page when you need everything
- `cat /openapi/openapi/phrase-tms-v3.json | jq '.paths | keys'` — list OpenAPI endpoints

OpenAPI specs for this site are mounted at: `/openapi/openapi/phrase-tms-v3.json`, `/openapi/openapi/phrase-tms-v1.json`, `/openapi/openapi/phrase-tms-latest.json`, `/openapi/openapi/phrase-tms-all.json`, `/openapi/openapi/phrase-tms-v2.json`, `/openapi/public/assets/openapi/phrase-strings.json`, `/openapi/openapi/phrase-strings.json`, `/openapi/openapi/phrase-tms-v4.json`, `/openapi/public/assets/openapi/phrase-byo-mt.yaml`, `/openapi/openapi/phrase-byo-mt.json`, `/openapi/public/assets/openapi/phrase-studio.json`, `/openapi/openapi/phrase-studio.json`, `/openapi/public/assets/openapi/phrase-connectors.yaml`, `/openapi/openapi/phrase-connectors.json`, `/openapi/public/assets/openapi/phrase-language-ai.yaml`, `/openapi/openapi/phrase-language-ai.json`, `/openapi/public/assets/openapi/phrase-control-hub.yaml`, `/openapi/openapi/phrase-control-hub.json`, `/openapi/public/assets/openapi/phrase-quality-evaluator-all.json`, `/openapi/openapi/phrase-quality-evaluator-all.json`, `/openapi/public/assets/openapi/phrase-style-guides.json`, `/openapi/openapi/phrase-style-guides.json`, `/openapi/public/assets/openapi/phrase-quality-evaluator-latest.json`, `/openapi/openapi/phrase-quality-evaluator-latest.json`, `/openapi/public/assets/openapi/phrase-platform.json`, `/openapi/openapi/phrase-platform.json`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication.

Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible.

When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.
- **submit_feedback** — Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Phrase MCP does

Phrase MCP gives an MCP-compatible AI assistant a structured way to investigate Phrase Developer Hub content. Its coverage includes documentation pages, code examples, API references, implementation guides, and the OpenAPI specifications mounted for Phrase products and services.

The server is focused on information retrieval and documentation feedback. It does not expose Phrase translation or terminology operations through the listed tools; its practical role is helping an agent find and inspect technical information about the Phrase platform.

## How it works

Use `search_phrase_developer_hub` for broad or conceptual questions. The search returns contextual excerpts, page titles, and direct documentation links, which helps an agent identify relevant material before opening a complete page.

For exact reading or investigation, use `query_docs_filesystem_phrase_developer_hub`. This tool presents a read-only, in-memory filesystem containing Phrase Developer Hub pages and OpenAPI specifications. Documentation pages are represented as `.mdx` files. After finding a page path, an agent can read it with commands such as `head` or `cat`; commands including `rg`, `tree`, `ls`, `jq`, and `sed` support focused searches and structural inspection.

Each filesystem call is stateless: the working directory resets to `/` between calls. Commands can inspect the virtual documentation store, but they cannot write files, access a real machine, run processes, or make network requests. Paths should be discovered with the search tool or filesystem navigation rather than guessed.

## Tools and capabilities

- Search the Phrase Developer Hub for concepts, API references, guides, examples, and feature information.
- Open a documentation page by reading its discovered `.mdx` path with `head` or `cat`.
- Search documentation files with exact keywords or regular expressions using read-only commands.
- Explore the documentation tree and list available files.
- Inspect mounted Phrase OpenAPI specifications, including endpoint definitions, schemas, parameters, and authentication details.
- Submit feedback about incorrect, outdated, confusing, incomplete, or broken documentation.

## Limitations and notes

The filesystem is a documentation sandbox, not a shell on the user’s computer or the server host. It contains Phrase Developer Hub pages and OpenAPI specifications only, and the available queries are read-only. Documentation feedback is intended for problems with the site’s content, not general product support or feedback about the MCP tool itself.

Because calls do not preserve state, navigation commands and file reads should be chained in one call when they depend on the same working directory. A reliable workflow is to search first, discover the exact path, then read or query that path.

_Full upstream README: https://allmcps.com/mcp/phrase-mcp/readme_