6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Translate text and files from your AI assistant using LILT's enterprise platform.
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 LILT MCP server lets Claude, ChatGPT or any MCP-compatible agent translate text and files through LILT's enterprise translation platform. Five tools cover machine translation, human-verified job submission, job status, download, and a balance reading. Sign-in is OAuth. One of those tools sends work to human translators and bills your contract.
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.
translate_files_with_verification as irreversible in effect, even if a job can be cancelled.scopes_supported is an empty array, so a user cannot grant read-only access and withhold the ability to spend.prompts/list.Yes, for translation work. LILT is a contracted enterprise platform billed per word at rates set in your agreement, and its quoting documentation states that every quote is an estimate and the final cost may vary. LILT publishes no per-tool price list and never uses the word credit anywhere in its 327-page documentation, so the balance figure's units are undocumented.
Yes, when verification is requested. LILT's developer documentation states plainly that Verified Translation has a human in the loop and that immediate turnaround is therefore not possible. A submitted job enters a workflow with named translator and reviewer stages, carries a contractual SLA due date, and produces a bill. The agent creates an obligation a person then fulfils.
Yes, and that ordering is the connector's best design decision. The directory lists get_credit_balance_information alongside the two translation tools, so a model can read available funds before committing to a submission. Most metered connectors in this catalogue expose no such preflight. LILT documents neither the tool nor what its numbers mean, so treat the reading as unspecified.
It depends which listing you followed, and the two disagree. Anthropic's directory names mcp.lilt.com/mcp; LILT's own MCP page names mcp-enterprise.lilt.com/mcp. Both hosts were live and both returned HTTP 401 to an anonymous request on 2026-08-19, and each advertises a completely different OAuth authorization server. Ask LILT which one your organization is provisioned against.
Yes, on your own models by design. LILT's platform builds customer-specific Contextual AI models from confirmed segments in your Data Sources, which is the product rather than a side effect. Segments a linguist marks as PII are excluded from the Data Source and from AI training, but LILT documents that exclusion as an organization setting an admin must enable.
Yes. LILT documents an organization-wide MCP toggle on a dedicated admin page, reached through Manage in the sidebar, that must be switched on before any user in the organization can connect an AI client. The same page lists every connected client, shows which users connected it, and lets an admin revoke individual connections.
It cannot deliver verified translation instantly, and it exposes no editing surface. LILT states verified work carries a human turnaround governed by your contractual SLA. The five listed tools cover submitting, checking and downloading only — nothing in the list edits segments, manages Data Sources, or assigns reviewers, all of which LILT's REST API does support.
.md suffix; this is the documentation URL in Anthropic's directory) · retrieved 2026-08-19support.lilt.com/robots.txt permits the docs path and carries Content-Signal: ai-train=yes, search=yes, ai-input=yes — synthesis is expressly permitted on all three axes (fetched 2026-08-19). lilt.com/robots.txt is Allow: / with tracking-parameter exclusions. The MCP host mcp.lilt.com/robots.txt is a blanket Disallow: /, which is a crawl rule on an API host and not a documentation source · retrieved 2026-08-19scopes_supported is an empty array · retrieved 2026-08-19https://blissful-celebration-62.authkit.app) · retrieved 2026-08-19https://mcp.lilt.com/mcp returns HTTP 401 with www-authenticate: Bearer error="invalid_token", resource_metadata="https://mcp.lilt.com/.well-known/oauth-protected-resource/mcp" · retrieved 2026-08-19https://mcp-enterprise.lilt.com/mcp returns HTTP 401; its descriptor at the path-append form names itself as authorization server and omits scopes_supported · retrieved 2026-08-19permissions field present) · retrieved 2026-08-16Connect LILT once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.