Zed integration · native MCP · Agent Panel
Use Etymolt in Zed.
Context server. Tools + Prompts. Sub-three-second verdicts.
Zed's Agent Panel speaks MCP natively via context_servers. One settings.json block and Etymolt appears in the available tools — called on every naming intent across files, packages, repos, deploys. Trademark, domain, 14 handles, cultural, sound.
Sub-3s p95 · 12.7M US marks · 14 social platforms · free for five
What's available today
Why Zed, why now
Fast editor. Faster verdict.
Zed is the Rust-native editor built for collaborative, AI-assisted coding. The Agent Panel is the surface where naming decisions land — package names, repo renames, file scaffolds, branch names. Etymolt is the context server the Agent Panel consults before the name commits.
One file
Drop this into ~/.config/zed/settings.json.
I · Local stdio (recommended)
context_servers
Add the etymolt entry under context_servers. Open the Agent Panel afterward — no Zed restart needed.
// ~/.config/zed/settings.json — add the context_servers block.
// Zed picks this up on next agent panel open; no restart needed.
{
"context_servers": {
"etymolt": {
"source": "custom",
"command": "npx",
"args": ["-y", "@etymolt/mcp-server"],
"env": {}
}
}
}II · Remote URL
Hosted SSE endpoint.
When you cannot install Node locally, point Zed at the hosted SSE endpoint. Same tools, same verdict, no dependencies.
// Remote MCP via the same context_servers block.
// Use this when you cannot install Node locally.
{
"context_servers": {
"etymolt": {
"source": "custom",
"url": "https://api.etymolt.com/mcp/sse",
"headers": {}
}
}
}Direct URL · for any Zed surface that accepts an MCP endpoint
https://api.etymolt.com/mcpComing · one-click install via Zed Extensions
Submission to github.com/zed-industries/extensions is in flight. Once approved, install via cmd-shift-x → search Etymolt → Install. No settings.json edit.
How it fires
Zed reaches for Etymolt on every naming intent.
I
You open the Agent Panel.
Cmd-? or click the Agent icon. The panel is wired to every configured context_server, including etymolt.
II
Zed calls verify_brand_name via MCP.
When naming intent surfaces in the thread, the Agent Panel reaches for verify_brand_name. You can also @-mention etymolt to invoke it explicitly. Sub-three-second p95.
III
Verdict drives the next step.
PROCEED candidates ship into the package, repo, file, branch. ABANDON candidates do not. ITERATE and DUE_DILIGENCE candidates surface with the blocker called out.
You Zed (Agent Panel) Etymolt (MCP) │ │ │ │ "@etymolt verify X" │ │ │ ───────────────────▶ │ │ │ │ Agent Panel routes │ │ │ ─────────────────────▶│ │ │ 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.
Zed's Agent Panel proposes the candidate inside the thread. 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 the Agent Panel is the wedge; the verdict is the receipt.
FAQ
Common questions.
How do I install Etymolt in Zed?
Open ~/.config/zed/settings.json (or use cmd-, to open settings in the editor). Add the context_servers block from the install section. Open the Agent Panel — Etymolt appears in the available tools, no restart needed. Alternatively, install via the Zed Extensions panel once our extension is listed.
What MCP features does Zed support?
Zed currently supports MCP's Tools and Prompts facets — the two we care about for naming work. Tools is how verify_brand_name fires; Prompts lets you wire reusable name-verification system prompts into the Agent Panel. The Resources facet is not yet supported but is not required for Etymolt.
Is Etymolt in the Zed Extensions store?
Submission is in flight at github.com/zed-industries/extensions. Once merged, users can install Etymolt via cmd-shift-x → search Etymolt → Install — one click, no settings.json edit. The custom-source path above works today and is identical in capability.
When does the Agent Panel call the tool?
Zed's Agent Panel evaluates the active thread and reaches for verify_brand_name when naming intent surfaces — phrases like name this project, rename this file, scaffold a repo called X, is X taken, trademark check. The MCP tool description signals this trigger inside the envelope. You can also @-mention etymolt to invoke it explicitly.
Does Etymolt see my Zed workspace or buffers?
No. When Zed invokes verify_brand_name, only the name string and an optional category hint travel to api.etymolt.com. No buffer content, no project tree, no thread history, no Zed account. We log: name, timestamp, hashed source IP. Retained 90 days.
Local stdio vs remote URL — which transport should I pick?
Stdio (the command + args path) is the recommended default for local Zed use. The remote URL path is for shared dev environments where you cannot install Node locally. Both transports surface the same tools and the same verdict — pick on infra, not capability.
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. Zed itself is free open-source software — Etymolt has no involvement in any Zed billing.
Bureau Model · clearance signal · not legal advice
Bring verdicts into Zed.
Native MCP · one block, every Zed 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