Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

Connect AI agents to the Phrase MCP server

Vendor MCP
Open markdown

The Phrase MCP connector routes your AI agent's tool calls to Phrase's own MCP server through Scalekit. Each user signs in to Phrase once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 38 tools.

Tools
38
What they doRead · write · destructive
28 · 1 · 928 read1 write9 destructive
Users sign in with
OAuth app
Your own Phrase MCP server app

Setup

  1. Install the SDK

    Terminal window
    npm install @scalekit-sdk/node dotenv
  2. Set your credentials

    Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.

    .env
    SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
    SCALEKIT_CLIENT_ID=<your-client-id>
    SCALEKIT_CLIENT_SECRET=<your-client-secret>
  3. Create the Phrase MCP connection

    In AgentKit > Connections, create a Phrase MCP connection and copy its redirect URI. The name you give it is the connection_name your code passes. See Configure connections.

  4. Register an OAuth app

    Phrase MCP server connections use your own OAuth app. Register one with Phrase MCP server and add the redirect URI you copied.

    Then enter the app's Client ID and Client Secret on the Phrase MCP connection.

  5. Authorize a user and make your first call

    quickstart.mts
    import { ScalekitClient } from '@scalekit-sdk/node'
    import 'dotenv/config'
    import { createInterface } from 'node:readline/promises'
    const scalekit = new ScalekitClient(
    process.env.SCALEKIT_ENVIRONMENT_URL,
    process.env.SCALEKIT_CLIENT_ID,
    process.env.SCALEKIT_CLIENT_SECRET,
    )
    const actions = scalekit.actions
    const connector = 'phrasemcp'
    const identifier = 'user_123'
    // Generate an authorization link for the user
    const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
    console.log('Authorize Phrase MCP:', link)
    const rl = createInterface({ input: process.stdin, output: process.stdout })
    await rl.question('Press Enter after authorizing...')
    rl.close()
    // Make your first call
    const result = await actions.executeTool({
    connector,
    identifier,
    toolName: 'phrasemcp_list_phrase_guides',
    toolInput: {},
    })
    console.log(result)
    Terminal window
    npx tsx quickstart.mts

    Each user signs in once. See Authorize a user for the full flow and statuses.

Tools

Pass the exact name to execute_tool
Try in PlaygroundRequest a tool
  • phrasemcp_connectors_read_apiForward a read-only Connectors API request.Read-only

    Connectors Read Api

    Forward a read-only Connectors API request. Use connectors_search_api to find the right operation, then supply the exact method and path from a search result. Only read-classified operations are accepted: GET/HEAD/OPTIONS requests, plus specific POST paths that the Connectors API models as reads (search, count, preview, and similar). For write or destructive operations (create, update, delete, import) use connectors_write_api instead.

    Inputs

    methodstringrequired
    HTTP method, e.g. GET, POST, PUT, PATCH, DELETE.
    pathstringrequired
    API path exactly as returned by the matching <product>_search_api tool, with path parameters filled in. Must come from a prior search result — never invented or version-substituted.
    allow_dropping_keysstring
    Escape hatch for a PUT that intentionally clears/omits some top-level fields the API last returned for this same resource (a full-replace PUT with no PATCH semantics resets any omitted field). Only needed if a PUT was blocked with `dropped_keys` in the response — pass those exact key names here to confirm the omission is deliberate.
    bodystring
    Optional JSON request body for POST/PUT/PATCH. For a multipart file-upload operation (a file_handle is supplied and the product uploads multipart, e.g. Language AI), the body object is sent as the `metadata` form part alongside the file — e.g. {"sourceLang":{"code":"en"},"targetLangs":[{"code":"cs"}],"actionTypes":[...]}.
    file_handlestring
    Optional file_handle token returned by PUT /mcp/uploads/{ticket}. Provide when the operation requires a file input (e.g. import/translate). Obtain it by calling request_upload_url first, then PUT the file bytes.
    headersstring
    Optional extra HTTP request headers as key-value pairs. Use when the API requires metadata in a header rather than the body — for example, the TMS job-import endpoint requires a Memsource header containing JSON job parameters: {"Memsource": "{\"targetLangs\":[\"de\"]}"}.
    query_paramsstring
    Optional query-string parameters as key-value pairs.
  • phrasemcp_connectors_search_apiSearch the standalone Phrase Connectors API docs — enterprise CMS integrations (Braze, Contentful, GitHub, Google Drive, Optimizely, Tridion Docs) that transfer file content through an already-configured connector.Read-only

    Connectors Search Api

    Search the standalone Phrase Connectors API docs — enterprise CMS integrations (Braze, Contentful, GitHub, Google Drive, Optimizely, Tridion Docs) that transfer file content through an already-configured connector. Use before connectors_read_api or connectors_write_api. show_full=true only when full requestBody schema needed. Connector lifecycle (create/list/get/patch/delete a connector) is a TMS operation — search tms_search_api instead.

    Inputs

    querystringrequired
    Keywords describing the operation you need, e.g. 'list projects', 'create translation job', 'export target file'.
    limitinteger
    Maximum number of operations to return. The output reports how many ranked matches were withheld by this limit.default 10
    show_fullboolean
    Return full request-body schemas instead of truncated ones. Use only when you need the full schema to build a request body.default false
  • phrasemcp_control_hub_read_apiForward a read-only Control Hub API request.Read-only

    Control Hub Read Api

    Forward a read-only Control Hub API request. Use control_hub_search_api to find the right operation, then supply the exact method and path from a search result. Only read-classified operations are accepted: GET/HEAD/OPTIONS requests, plus specific POST paths that the Control Hub API models as reads (search, count, preview, and similar). For write or destructive operations (create, update, delete, import) use control_hub_write_api instead.

    Inputs

    methodstringrequired
    HTTP method, e.g. GET, POST, PUT, PATCH, DELETE.
    pathstringrequired
    API path exactly as returned by the matching <product>_search_api tool, with path parameters filled in. Must come from a prior search result — never invented or version-substituted.
    allow_dropping_keysstring
    Escape hatch for a PUT that intentionally clears/omits some top-level fields the API last returned for this same resource (a full-replace PUT with no PATCH semantics resets any omitted field). Only needed if a PUT was blocked with `dropped_keys` in the response — pass those exact key names here to confirm the omission is deliberate.
    bodystring
    Optional JSON request body for POST/PUT/PATCH. For a multipart file-upload operation (a file_handle is supplied and the product uploads multipart, e.g. Language AI), the body object is sent as the `metadata` form part alongside the file — e.g. {"sourceLang":{"code":"en"},"targetLangs":[{"code":"cs"}],"actionTypes":[...]}.
    file_handlestring
    Optional file_handle token returned by PUT /mcp/uploads/{ticket}. Provide when the operation requires a file input (e.g. import/translate). Obtain it by calling request_upload_url first, then PUT the file bytes.
    headersstring
    Optional extra HTTP request headers as key-value pairs. Use when the API requires metadata in a header rather than the body — for example, the TMS job-import endpoint requires a Memsource header containing JSON job parameters: {"Memsource": "{\"targetLangs\":[\"de\"]}"}.
    query_paramsstring
    Optional query-string parameters as key-value pairs.
  • phrasemcp_control_hub_search_apiSearch Control Hub API docs.Read-only

    Control Hub Search Api

    Search Control Hub API docs. Use before control_hub_read_api or control_hub_write_api. Currently covers content groups — an organisation-scoped coordination layer that links a TMS project to shared Style Guides, Style Rules, and Quality Evaluation checks (Rules themselves are created and edited in the Style Guides product, not here). show_full=true only when full requestBody schema needed.

    Inputs

    querystringrequired
    Keywords describing the operation you need, e.g. 'list projects', 'create translation job', 'export target file'.
    limitinteger
    Maximum number of operations to return. The output reports how many ranked matches were withheld by this limit.default 10
    show_fullboolean
    Return full request-body schemas instead of truncated ones. Use only when you need the full schema to build a request body.default false
  • phrasemcp_kb_lookupLook up a specific Help Center section by title, or by the id kb_search shows for a shared title — returns its summary, key concepts, tasks, and related topics.Read-only

    Kb Lookup

    Look up a specific Help Center section by title, or by the id kb_search shows for a shared title — returns its summary, key concepts, tasks, and related topics. Use after kb_search when you know the section name.

    Inputs

    titlestringrequired
    Exact or partial title of the documentation section to look up. The search is case-insensitive. Examples: 'Jobs overview', 'Translation memories', 'User management'. When a search result shows an id (its title is shared by several sections), pass the id.
  • phrasemcp_kb_pageRetrieve the full content of a Help Center page (procedures, code samples), optionally including subsections.Read-only

    Kb Page

    Retrieve the full content of a Help Center page (procedures, code samples), optionally including subsections. Use when you need complete documentation, not just a summary. When a kb_search result shows an id (its title is shared by several sections), pass that id. Never call this tool twice with the same title in one turn — a repeat call with no new argument returns identical content and wastes a round.

    Inputs

    titlestringrequired
    Title or section ID of the documentation page to retrieve. Case-insensitive title matching is used. When a search result shows an id (its title is shared by several sections), pass that id so you get that section rather than another one with the same title.
    depthinteger
    Maximum depth for recursive retrieval when recursive=true. 1 = children only, 2 = children and grandchildren (default). Higher values retrieve deeper nested content.default 2
    include_metadataboolean
    Whether to include metadata header (product, parent, features) at the top of the output. Set to false for raw content only.default true
    recursiveboolean
    Whether to include child sections (subsections) in the output. Set to true (default) for comprehensive documentation including all subsections. Set to false to retrieve only the main section.default true
  • phrasemcp_language_ai_read_apiForward a read-only Language AI API request.Read-only

    Language Ai Read Api

    Forward a read-only Language AI API request. Use language_ai_search_api to find the right operation, then supply the exact method and path from a search result. Only read-classified operations are accepted: GET/HEAD/OPTIONS requests, plus specific POST paths that the Language AI API models as reads (search, count, preview, and similar). For write or destructive operations (create, update, delete, import) use language_ai_write_api instead.

    Inputs

    methodstringrequired
    HTTP method, e.g. GET, POST, PUT, PATCH, DELETE.
    pathstringrequired
    API path exactly as returned by the matching <product>_search_api tool, with path parameters filled in. Must come from a prior search result — never invented or version-substituted.
    allow_dropping_keysstring
    Escape hatch for a PUT that intentionally clears/omits some top-level fields the API last returned for this same resource (a full-replace PUT with no PATCH semantics resets any omitted field). Only needed if a PUT was blocked with `dropped_keys` in the response — pass those exact key names here to confirm the omission is deliberate.
    bodystring
    Optional JSON request body for POST/PUT/PATCH. For a multipart file-upload operation (a file_handle is supplied and the product uploads multipart, e.g. Language AI), the body object is sent as the `metadata` form part alongside the file — e.g. {"sourceLang":{"code":"en"},"targetLangs":[{"code":"cs"}],"actionTypes":[...]}.
    file_handlestring
    Optional file_handle token returned by PUT /mcp/uploads/{ticket}. Provide when the operation requires a file input (e.g. import/translate). Obtain it by calling request_upload_url first, then PUT the file bytes.
    headersstring
    Optional extra HTTP request headers as key-value pairs. Use when the API requires metadata in a header rather than the body — for example, the TMS job-import endpoint requires a Memsource header containing JSON job parameters: {"Memsource": "{\"targetLangs\":[\"de\"]}"}.
    query_paramsstring
    Optional query-string parameters as key-value pairs.