Bring N Gram Analysis
to Cursor
Learn how to connect Language Detector Engine to Cursor and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Language Detector Engine MCP Server?
Your customer support agent receives a ticket: 'O produto não chegou'. The AI routes it to the Spanish queue. The agent wastes time, the customer gets angry, SLA drops. Why? Because the AI 'guessed' the language probabilistically instead of calculating it.
This MCP uses franc (200K+ weekly downloads, inspired by Google's CLD2) to perform deterministic N-gram language detection. It returns exact ISO 639-3 codes for over 400 languages, and properly returns 'undefined' if a text is too ambiguous rather than hallucinating.
The Superpowers
- 400+ Languages: From English (eng) and Portuguese (por) to Esperanto (epo) and Zulu (zul).
- Exact N-gram Math: Analyzes text strictly by character frequencies, not LLM probability.
- Whitelist/Blacklist: Know the text must be either Spanish or Portuguese? Pass
only: ['spa', 'por']to force a strict evaluation. - Confidence Scores: Use the
allflag to get an array of all matches with their exact probability scores.
Built-in capabilities (1)
Provide as much text as possible for higher accuracy. Detect the language of any text using n-gram analysis. Supports 400+ languages. Returns ISO 639-3 codes (e.g., "por", "eng", "spa")
Why Cursor?
Cursor's Agent mode turns Language Detector Engine into an in-editor superpower. Ask Cursor to generate code using live data from Language Detector Engine and it fetches, processes, and writes. all in a single agentic loop. 1 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Language Detector Engine in Cursor
Language Detector Engine and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Language Detector Engine to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Language Detector Engine in Cursor
The Language Detector Engine MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Language Detector Engine for Cursor
Every tool call from Cursor to the Language Detector Engine MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Why is this better than asking Claude to detect the language?
LLMs often hallucinate languages for short strings or names. They also struggle to provide standardized ISO codes reliably. This engine uses mathematical N-gram analysis (the same technique behind Google Search language detection) to deterministically map text to one of 400+ ISO 639-3 codes.
What does it mean if it returns 'und'?
'und' stands for Undefined. It means the text is too short, mostly numbers, or too ambiguous to confidently map to a single language. This is a feature — it prevents your routing logic from making false assumptions.
Can I force it to choose between specific languages?
Yes. Pass an array of ISO 639-3 codes to the 'only' parameter (e.g., ['eng', 'por', 'spa']). The engine will only calculate probabilities within that subset.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Cradl AI
10 toolsEquip your AI agent to extract structured data from any document using Cradl AI's deep learning models.
Clio
12 toolsPractice law more efficiently with legal case management, time tracking, billing, and document organization in one system.
OptimoRoute
10 toolsOptimize delivery routes via OptimoRoute — create orders, track driver locations, and manage route planning directly from any AI agent.
Audienceful
10 toolsManage subscribers, custom fields, and email automations via Audienceful — orchestrate newsletters and campaigns directly via AI.