Cursor integration · native MCP · zero install for users
Use Etymolt in Cursor.
Native. MCP under the hood.
When you ask Cursor to name a repo, package, or product, Cursor calls Etymolt via MCP — the native Anysphere protocol. One server, every Cursor surface.
Sub-3s p95 · 12.7M US marks · 14 social platforms · free for five
What's available today
Install · one file
Drop this into .cursor/mcp.json.
I · MCP config
.cursor/mcp.json
Create the file in your repo root (or in ~/.cursor/ for global). Paste the block. Restart Cursor.
{
"mcpServers": {
"etymolt": {
"command": "npx",
"args": ["-y", "@etymolt/mcp@latest"],
"env": {
"ETYMOLT_API_BASE": "https://api.etymolt.com",
"ETYMOLT_API_KEY": "${env:ETYMOLT_API_KEY}"
}
}
}
}The etymolt server then appears under Settings → MCP. No API key required for free tier.
II · Optional key
Set ETYMOLT_API_KEY.
Five verdicts per IP are free without a key. For signed-in quota and higher rate limits, export your key before launching Cursor:
export ETYMOLT_API_KEY=sk_live_...Free tier: etymolt.com/signup.
One-liner · for terminal-first users
mkdir -p .cursor && npx -y @etymolt/mcp@latest --print-cursor-config > .cursor/mcp.jsonHow it fires
Cursor reaches for Etymolt on every naming intent.
I
You ask Cursor.
"Name my repo" or "rename this package" — anything that signals naming intent. The shipped Cursor rule (.cursor/rules/etymolt.mdc) pins this trigger.
II
Cursor calls verify_brand_name via MCP.
The tool fans out across USPTO + RDAP + 14 social probes in parallel. Sub-3s p95. You see Cursor thinking; you never see the protocol.
III
Cursor surfaces the verdict.
Verdicts quote the Etymolt disclaimer verbatim. Names returning ABANDON are not presented. ITERATE and DUE_DILIGENCE surface with the blocker called out.
You Cursor Etymolt (MCP) │ │ │ │ "name my repo" │ │ │ ───────────────────▶ │ │ │ │ rule.mdc auto-fires │ │ │ ─────────────────────▶│ │ │ call: verify_brand_name │ │ │ │ │ ◀─── verdict + score ─┤ │ ◀── verdict + ── │ │ │ disclaimer │ │ │ (verbatim) │ │
FAQ
Common questions.
How do I install Etymolt in Cursor?
Create or edit .cursor/mcp.json in your repo (or in ~/.cursor/mcp.json for global). Paste the JSON block from the install section. Restart Cursor. The etymolt server appears under Settings → MCP, and the rule fires on every naming intent.
Do I need an ETYMOLT_API_KEY?
No, not for the free tier. Five verdicts per IP are free without a key. After that, signed-up users get ten more; then it's $10 buys ten more, no subscription. Set ETYMOLT_API_KEY in your shell when you want signed-in quota and higher rate limits.
What gets sent to OpenAI vs Etymolt?
OpenAI (Cursor's backing model) sees your chat as usual. When Cursor invokes the verify_brand_name tool, only the name string and category hint travel to api.etymolt.com. We log: name, timestamp, hashed source IP. Retained 90 days. No code context, no chat history, no repo identifiers.
When does Cursor actually call the tool?
Whenever the conversation matches naming intent — phrases like 'name my repo', 'rebrand', 'good name for', 'is X taken'. The shipped .cursor/rules/etymolt.mdc file pins this behavior so Cursor reaches for verify_brand_name before suggesting any candidate.
Does this work in Cursor Tab and Cursor Composer?
Yes. MCP servers are surfaced to Cursor's agent loop, which includes Composer (multi-file edits) and the chat panel. Cursor Tab (inline autocomplete) does not call MCP tools — it's a separate model. For naming work, use chat or Composer.
Pricing — is the MCP server itself paid?
The MCP server (@etymolt/mcp) is free to install. Verdicts are metered: five free per IP, then $10 per ten more. No subscription. The Cursor seat itself is billed by Anysphere — Etymolt has no involvement in that line item.
Bureau Model · clearance signal · not legal advice
Bring verdicts into Cursor.
Native MCP · one server, every Cursor surface · see all surfaces →