Claude Desktop now logs into your MCP server with a click. Until this week, you copied an API key out of the dashboard, pasted it into the client config, and re-pasted it every time the key rotated. The server now speaks browser-redirect OAuth (RFC 8252 §7.3): the client opens a tab, you confirm, you're in. Engines are configurable from inside the client too – see the MCP capabilities reference.
Also shipped#
lockedKeyson the async API. Slugs, IDs, URL parameters, and any value that's structural metadata rather than translatable content stay verbatim across target locales and bypass the LLM entirely.- Sync localize returns usage metrics per call. The model used, the LLM cost, and the localization token cost ride back in the response, so you can attribute translation cost down to a single end user.
- Logs show the context that produced each translation. Open any request in the Log tab and you can see exactly which glossary terms, instructions, and brand-voice rules the engine retrieved – plus the glossary review reasoning.
- Cost-by-model report. New chart on the Reports page splits cost and token usage by model across configured engines.
- Pipeline tab is always visible, with feature gates inline rather than hiding the whole surface.