Accounts, projects, jobs, translation data, glossaries, style guides, translation memory, and other linguistic assets.
Smartling
A leading enterprise localization platform with APIs, connectors, workflows, jobs, content, translations, and quality operations that can be embedded into larger content-production interfaces.
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Retrieve account users, projects, jobs, translations, glossaries, style guides, linguistic packages and translation memory; search glossary terms and inspect file or translation status locally.
Translate text, add or remove string tags, authorize jobs and add strings remotely; locally upload, download, rename or delete files and run machine translation.
Remote static tokens remain supported through August 3, 2026, then OAuth 2.1 becomes required. Local Docker uses Smartling user ID, secret and project ID.
Deselect unneeded account-wide tools, verify MT profile and linguistic assets, and review job authorization, string additions, tags, local uploads, downloads, renames, deletions and machine translation.
Remote MCP cannot upload or download project files and only has limited small-text-file support. Full file workflows require local Docker with a mounted `/smartling` directory.
Agent access
MCP support
Support: Official MCP server
Read scope: Expose only permitted account, project, job, translation and linguistic-asset reads, preserving project, locale, source string, translation memory, glossary, style guide and provider context.
Write scope: Separate remote instant text and job actions from local file movement and CLI commands; preview target project, locales, MT profile, assets and file operation before execution.
Authentication: Until August 3, remote clients may send an Account Owner-created static token; from that date Smartling requires browser OAuth 2.1. Local Docker retains API credentials.
Approval boundary: Confirm project, locales, source version, MT profile, glossary and style guide before translation; separately approve job authorization, string changes and every local file mutation.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Smartling ships them.
Single-platform patterns
- Global campaign localization command center
- Media production console
- Localization and variant studio
- Review-and-approval queue
Multi-platform compositions
- Smartling + publishing or campaign platform: media production console
- Smartling + DAM or CMS + social or video distribution system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
4 recorded sources
Smartling documents a remote account-connected server and a separate Docker-based CLI MCP for file workflows.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Product overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party event documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.