MCP server

The FluentC MCP server gives any agent that speaks the Model Context Protocol a translation tool. The agent decides when to translate; you don't write glue code.

• Server URL: https://mcp.fluentc.ai
• Authentication: your FluentC API key in the Authorization header, sent as-is with no Bearer prefix, the same as the REST API.
• Plan and languages: the same as the REST API. The server uses your key's languages and plan.

Connect a client

You need an API key. Add FluentC as a remote MCP server in your client.

Claude Code

claude mcp add --transport http fluentc https://mcp.fluentc.ai \
  --header "Authorization: YOUR_FLUENTC_KEY"

Cursor and other clients with a JSON config

Most MCP clients take a JSON entry like this (Cursor reads it from .cursor/mcp.json):

{
  "mcpServers": {
    "fluentc": {
      "url": "https://mcp.fluentc.ai",
      "headers": { "Authorization": "YOUR_FLUENTC_KEY" }
    }
  }
}

Keep the key out of files you commit. Use your client's support for environment variables or a secrets store where it has one.

Any other client

Point it at https://mcp.fluentc.ai as a remote HTTP server and set one request header, Authorization, to your key. Check your client's documentation for where headers go.

Check the connection

The MCP Inspector connects to a server and lists what it offers:

npx @modelcontextprotocol/inspector

Enter https://mcp.fluentc.ai as the server URL, add the Authorization header, and connect. You should see FluentC's tools listed.

What the agent sees

When a client connects, the server lists its tools, each with a name, a description and an input schema. Your client shows the current set and the agent chooses among them, so the tool list here never goes stale. The tools wrap the same operations as the REST API, so the same rules apply:

• Languages are lowercase two- or three-letter codes, and must be enabled for your key. See Languages.
• Real-time translation needs the Real-time plan. Batch needs a job to be polled for its result. See Concepts.
• Repeated text is answered from translation memory.

Prompting an agent

Agents translate best when the request is specific.

• Name the target language: "translate this into Japanese" or "into ja".
• Say what the text is if it matters: UI label, legal notice, chat message.
• For a lot of text, ask for batch mode and say it can wait for the result.

Troubleshooting

If it still doesn't work, contact us with your client's name and the error text.