Lingo.dev
Day 18 after signup
W44 Product Update: Set up engines, bulk-edit glossaries, and check quality in MCP
Engine setup, bulk glossary edits, and quality measurements in one MCP connection.
Why it works
- Lead with a concise overview of the release so readers can quickly see the main areas covered.
- Give each capability its own section and explain the practical task it makes easier.
- End with one clear link to the full changelog for readers who want more detail.
How it is built
- Update headline
- Engine setup details
- Bulk glossary editing
- Quality and organization updates
Email copy
New in the Lingo.dev MCP server: engine provisioning, bulk glossary edits, quality measurements, and one connection for every organization. Provision engines from your website. Give your AI assistant your website URL to create a new engine with a generated glossary, ruleset, and brand voice. For existing engines, fill context that’s missing without changing existing content. Track each job’s progress as it runs in the background, and retry any part that fails. Update or delete glossary terms in bulk. Change or remove up to 100 terms in one call, instead of one term per call. This makes large glossaries faster to maintain when you set up a new engine or migrate from another vendor. If some terms fail, the rest are still saved. Read translation quality measurements. See which engines and languages each measurement covers, find low-scoring translations, and read the explanation behind any result. Use one connection for every organization. One MCP connection now covers every organization your account belongs to. Your AI assistant asks which one to use and acts with your permissions in each, so you no longer need to reconnect to switch. Read the full changelog → – Veronica Lingo.dev · San Francisco, CA Unsubscribe