Continue.dev integration · YAML or JSON · agent mode
Use Etymolt in Continue.
One YAML file. Drop it in. Agent mode picks it up.
Continue.dev is the open-source AI assistant for VSCode and JetBrains. The MCP surface gates to Agent mode — one .continue/mcpServers/etymolt.yaml and the verdict fires before your project name lands in any repo, package, or deploy.
Sub-3s p95 · 12.7M US marks · 14 social platforms · free for five
What's available today
Why Continue, why now
Open-source assistant. Open standard verdict.
Continue.dev runs in VSCode and JetBrains under the model you choose — OpenAI, Anthropic, Mistral, Ollama, anything that speaks the OpenAI-compatible chat API. Whichever model is driving the prompt, Etymolt is the verification primitive that fires when naming intent appears. The YAML drop-in works identically across providers.
Three install paths
YAML per-workspace, block in config, or paste the Claude JSON.
I · YAML (recommended)
.continue/mcpServers/
Drop this YAML at .continue/mcpServers/etymolt.yaml in your workspace. Gitable, per-workspace, no global state.
# .continue/mcpServers/etymolt.yaml — recommended path.
# Continue picks up every YAML in .continue/mcpServers/ automatically.
name: etymolt
version: 0.1.0
schema: v1
mcpServers:
- name: etymolt
command: npx
args:
- "-y"
- "@etymolt/mcp-server"
# Optional. Five anonymous verdicts per IP are free without a key.
# env:
# ETYMOLT_API_KEY: ${{ secrets.ETYMOLT_API_KEY }}II · Global config
~/.continue/config.yaml
Add to the global Continue config so every workspace inherits the etymolt server. Useful when you switch between repos often.
# Inside ~/.continue/config.yaml — global registration.
# Continue inherits this in every workspace.
mcpServers:
- name: etymolt
command: npx
args: ["-y", "@etymolt/mcp-server"]III · Cross-format
Reuse Claude / Cursor JSON.
Already have Etymolt in Claude Desktop, Cursor, or Cline? Drop the same JSON into .continue/mcpServers/etymolt.json.
# Continue accepts Claude Desktop / Cursor / Cline JSON files.
# Drop this verbatim into .continue/mcpServers/etymolt.json.
{
"mcpServers": {
"etymolt": {
"command": "npx",
"args": ["-y", "@etymolt/mcp-server"]
}
}
}Direct URL · for any Continue surface that accepts MCP endpoints
https://api.etymolt.com/mcpHow it fires
Continue reaches for Etymolt on every naming intent.
I
Switch to Agent mode.
Continue gates MCP tools to Agent mode. Open the model picker in the bottom-right and choose any model in Agent mode before naming work begins.
II
Continue calls verify_brand_name via MCP.
Etymolt fans out across USPTO + RDAP + 14 social probes in parallel. Sub-three-second p95. Continue surfaces the verdict in chat with the disclaimer quoted verbatim.
III
Verdict drives the next step.
PROCEED candidates ship into your code, package.json, repo, deploy. ABANDON candidates do not. ITERATE and DUE_DILIGENCE candidates surface with the blocker called out.
You Continue (Agent) Etymolt (MCP) │ │ │ │ "name this repo" │ │ │ ───────────────────▶ │ │ │ │ naming intent fires │ │ │ ─────────────────────▶│ │ │ call: verify_brand_name │ │ │ │ │ ◀─── verdict + score ─┤ │ ◀── verdict + ── │ │ │ disclaimer │ │ │ (verbatim) │ │
The validation stack
Five axes. One signed verdict.
Trademark
USPTO · TTAB · UKIPO · Madrid
Domain & handles
RDAP · WHOIS · 14 platforms
Cultural
7 languages · 20 markets
Linguistic
1.4M-name distinctiveness corpus
Sound symbolism
12 perceptual axes · TTS round-trip
What we are NOT
We don't generate names. We validate them.
Continue's configured model proposes the candidate. Etymolt verifies it across five axes against live ground truth. The two products sit cleanly on different sides of the workflow. The naming moment in Continue is the wedge; the verdict is the receipt.
FAQ
Common questions.
How do I install Etymolt in Continue.dev?
Two paths. (1) Drop a YAML file at .continue/mcpServers/etymolt.yaml in your workspace — Continue picks it up automatically. (2) Add an mcpServers block to your global ~/.continue/config.yaml so every workspace inherits it. Both surface the etymolt tools under Agent mode.
Does Continue speak MCP everywhere, or only in agent mode?
Only in agent mode. Continue gates MCP tools to its Agent surface so that regular chat completions cannot accidentally fire side-effects. Verify_brand_name is read-only, but the gate applies to every MCP server uniformly. Switch to Agent mode in the bottom-right model picker before naming work.
Can I reuse my Claude Desktop or Cursor MCP file?
Yes. Continue accepts the standard MCP JSON format. Drop the same Claude/Cursor/Cline mcpServers JSON block into .continue/mcpServers/etymolt.json and Continue picks it up. This is the lowest-friction install path if you already have Etymolt running in any other MCP client.
Do I need an ETYMOLT_API_KEY?
No, not for the free tier. Five verdicts per IP are free without a key. For higher quota and signed-in verdicts, export ETYMOLT_API_KEY before launching VSCode / JetBrains, or reference it via Continue Mission Control secrets so the value never lands in source control.
When does Continue actually call the tool?
Continue's Agent mode evaluates the active conversation and reaches for verify_brand_name when the context matches naming intent — phrases like name this project, rename this package, is X taken, trademark check, good name for. The tool description signals this trigger inside the MCP envelope.
Does Etymolt see my Continue chat or code?
No. When Continue invokes verify_brand_name, only the name string and an optional category hint travel to api.etymolt.com. No chat history, no code context, no workspace identifiers, no model provider details. We log: name, timestamp, hashed source IP. Retained 90 days.
What does this cost?
Five verdicts per IP are free. Signed-up users get ten more on the house. After that, ten dollars buys ten more. No subscription. Continue itself is free open-source software — Etymolt has no involvement in any Continue billing.
Bureau Model · clearance signal · not legal advice
Bring verdicts into Continue.
Open-source MCP · one YAML, every Continue workspace · see all surfaces →
Clearance signal, not legal advice. Confirm with trademark counsel before adopting a name in commerce. Data sources have stated freshness windows; refer to coverage_caveat per jurisdiction.
NPM · @etymolt/mcp-server