6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Machine translate text, manage translation jobs and triage quality issues.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Smartling MCP server connects a Smartling translation account to Claude, ChatGPT, Cursor, VS Code and any MCP-compatible agent. It exposes 51 tools covering machine translation, glossaries, style guides, translation memory, jobs, strings and quality issues — so localization teams translate and triage in conversation instead of in the Smartling dashboard.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
smartling_authorize_job releases content to translation vendors at agreed rates. Smartling states a cancelled or deleted job cannot be undone and that you may still be liable for work already performed. This is the single highest-consequence tool on the connector.offline_access alone — a refresh-token mechanism, not a permission. There is no read-only variant of this connection to approve at consent time. Constrain access through the Smartling role you connect with.plain is still accepted. The authorization server advertises both S256 and plain as code challenge methods. plain offers materially weaker protection than S256.smartling-cli-mcp for file workflows.Smartling documents no plan gate on the connector. Its Growth versus Enterprise comparison covers roles, workflows, linguistic assets and machine translation without mentioning MCP at all. What the docs do gate is the role: using every available tool requires the Account Owner role, and other users reach only the tools their own permissions allow.
Yes, through two separate paths. Authorizing a translation job releases content to your translation vendors at agreed rates, and Smartling warns that a cancelled job may still leave you liable for work already done. Separately, instant machine translation counts toward your account's AI Hub usage, tracked in the AI Hub Usage Report.
Not cleanly. Cancelling unauthorizes in-progress strings and unassigns linguists, but Smartling states plainly that a cancelled or deleted job cannot be undone, and that you may be liable for translation costs already incurred. Published strings stay published. Treat authorization as a commitment rather than a reversible state change.
No. Smartling's documentation attributes this to MCP security restrictions that prevent uploading files to remote servers, and describes only limited support for small text-formatted files. For file-based workflows Smartling publishes a separate local Docker product, smartling-cli-mcp, which mounts a folder on your own machine.
No. Smartling states that no files or text are uploaded to a Smartling project, translations are not saved to translation memory, and content does not pass through a translation workflow. There is no human in the loop. Smartling also states that requested content is not stored or ingested into Smartling.
One, and it is not an application scope. Both of the server's OAuth discovery documents advertise offline_access alone, which only requests a refresh token. No scope describes what the connector may read or change, so the consent screen has nothing to narrow. Authorisation comes from your Smartling account role instead.
Not to connect, but to reach everything. Smartling documents that the server exposes both project-level and account-level tools, that using every available tool requires the Account Owner role, and that users without it can still authenticate and use the tools their permissions allow. Account Owner is the highest-permission Smartling role.
https://mcp.smartling.com/mcp — an anonymous initialize returns HTTP 401 with WWW-Authenticate: Bearer resource_metadata= "https://mcp.smartling.com/.well-known/oauth-protected-resource/mcp". That RFC 9728 descriptor returns HTTP 200 with authorization_servers: ["https://mcp.smartling.com"] and scopes_supported: ["offline_access"]. The server's /.well-known/oauth-authorization-server document also returns HTTP 200, lists the same single scope, and adds registration_endpoint /auth/register, the authorization_code and refresh_token grants, and code_challenge_methods_supported: ["plain", "S256"]. Our own observation, 2026-08-18. This is why no tool descriptions or parameter schemas appear on this page: the handshake never reached tools/list. · retrieved 2026-08-18/api/v2/help_center/articles/search.json) returns two MCP articles across the whole knowledge base, neither listing tool names, and Smartling/smartling-cli-mcp is the organisation's only MCP repository on GitHub — that being the Docker CLI product, not this server. developers.smartling.com does not resolve. So the directory's 51 names cannot be diffed against a vendor list in either direction, and the count here is single-sourced by necessity (checked 2026-08-18). · retrieved 2026-08-18robots.txt for help.smartling.com (HTTP 200, retrieved 2026-08-18). A Zendesk policy that disallows administrative and search paths but permits /hc/*/articles/, and carries no Content-Signal directive, so fetching and synthesis are both unrestricted. www.smartling.com/robots.txt (HTTP 200) likewise disallows only HubSpot preview paths. Neither host serves an llms.txt (both HTTP 404 or redirect). · retrieved 2026-08-18help.smartling.com returns HTTP 403 to a default command-line user agent while returning HTTP 200 to a browser user agent for the same article paths. That is bot-blocking, not policy — robots.txt expressly permits these paths. Every article above was read through Zendesk's own public Help Center API (/api/v2/help_center/en-us/articles/<id>.json), and each article URL printed here is the canonical html_url returned by that API, confirmed to resolve HTTP 200 (2026-08-18). · retrieved 2026-08-18Connect Smartling once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.