Cline integration · MCP Marketplace · autonomous agent
Use Etymolt in Cline.
One-click install from the Cline MCP Marketplace.
Cline runs autonomous coding loops inside VSCode — agentic edits, scaffolds, package renames. Etymolt fires before the loop commits a name to disk. Trademark, domain, 14 handles, cultural, sound — sub-three-second p95, signed verdict.
Sub-3s p95 · 12.7M US marks · 14 social platforms · free for five
What's available today
Why Cline, why now
Autonomous loops need verified inputs. Etymolt is the input check.
Cline runs multi-step coding loops — reads files, edits packages, renames repos, scaffolds new projects. Inside that loop, when a name needs to ship, the loop should not guess. Etymolt is the verdict the loop consults before commit. One tool call, one signed verdict, sub-three-second p95.
Two install paths
Marketplace one-click, or manual JSON.
I · Marketplace
One-click install.
- Open the Cline panel in VSCode.
- Click the stacked-server icon in the top toolbar of the panel.
- Open the Marketplace tab.
- Search for Etymolt.
- Click Install.
No config file, no JSON. Marketplace listing is in submission — the manual path below works today.
II · Manual JSON
Configure MCP Servers.
Same icon → Configure tab → Configure MCP Servers. Paste this block.
{
"mcpServers": {
"etymolt": {
"command": "npx",
"args": ["-y", "@etymolt/mcp-server"],
"env": {
"ETYMOLT_API_KEY": ""
},
"disabled": false,
"autoApprove": ["verify_brand_name"]
}
}
}autoApprove skips the confirm prompt for read-only verify_brand_name calls.
Alternative · Remote SSE transport
If you cannot install Node locally, point Cline at the hosted SSE endpoint. Same tools, same verdict, no npx.
{
"mcpServers": {
"etymolt": {
"transport": {
"type": "sse",
"url": "https://api.etymolt.com/mcp/sse"
},
"disabled": false,
"autoApprove": ["verify_brand_name"]
}
}
}How it fires
Cline reaches for Etymolt inside the agent loop.
I
Cline runs the loop.
Cline reads the task, plans, and executes — multi-step edits, package renames, repo scaffolds. The loop encounters a naming decision.
II
Cline calls verify_brand_name via MCP.
Etymolt fans out across USPTO + RDAP + 14 social probes in parallel. Sub-three-second p95. With autoApprove enabled, no confirm prompt fires.
III
Verdict gates the commit.
PROCEED candidates land in the package, repo, or deploy. ABANDON candidates do not. ITERATE and DUE_DILIGENCE candidates surface with the blocker called out so the loop can pick again.
You Cline (loop) Etymolt (MCP) │ │ │ │ "scaffold X repo" │ │ │ ───────────────────▶ │ │ │ │ agent loop runs │ │ │ ─────────────────────▶│ │ │ 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.
Cline's configured model proposes the candidate inside the agent loop. Etymolt verifies it across five axes against live ground truth. The two products sit cleanly on different sides of the workflow. The naming moment inside the loop is the wedge; the verdict is the receipt.
FAQ
Common questions.
How do I install Etymolt in Cline?
Two paths. (1) Open the Cline panel in VSCode, click the stacked-server icon in the top toolbar, open the Marketplace tab, search Etymolt, click Install. One click, no config file. (2) Manual: same icon, Configure tab, Configure MCP Servers, paste the mcpServers JSON block from the install section. Both surface the etymolt tools immediately.
Is Etymolt in the Cline MCP Marketplace?
Submission to github.com/cline/mcp-marketplace is in flight. Cline's review team aims to merge within a few days. Until live, the manual JSON path installs the same server with identical behavior. Marketplace listing is the one-click-discovery upside, not a different integration.
What does autoApprove do?
Cline's autoApprove field is a per-tool whitelist that skips the confirmation prompt for safe, read-only tools. We recommend autoApprove: ["verify_brand_name"] so the verdict fires automatically when Cline reaches for it — verify_brand_name is read-only by design. Leave autoApprove empty if you want to confirm every call.
When does Cline actually call the tool?
Cline's agent loop evaluates the active conversation and reaches for verify_brand_name when naming intent appears — phrases like name this project, rename this package, scaffold a repo called X, is X taken, trademark check. The MCP tool description signals this trigger inside the envelope.
Does Etymolt see my Cline workspace or code?
No. When Cline invokes verify_brand_name, only the name string and an optional category hint travel to api.etymolt.com. No workspace code, no chat history, no repo identifiers, no model provider details. We log: name, timestamp, hashed source IP. Retained 90 days.
Stdio vs remote SSE — which transport should I pick?
Stdio (the npx command path) is the default and recommended path for local Cline use. The remote SSE path connects to https://api.etymolt.com/mcp/sse and is the right choice when you cannot install Node locally or when you want to share the same MCP context across multiple machines. Both transports surface the same tools.
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. Cline itself is free open-source software — Etymolt has no involvement in any Cline billing.
Bureau Model · clearance signal · not legal advice
Bring verdicts into Cline.
Marketplace MCP · one click, every Cline 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