Power your agent
Yayıncının kendi komutu. PlugMCP uç noktası değildir.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code'un yerel komutlar için kurulum bağlantısı yok. Aşağıdaki komutu kopyalayın ve bir terminalde çalıştırın.
claude mcp add codemode-lsp -- npx -y codemode-lsp@0.4.2Bir terminalde çalıştırın.
{ "mcpServers": { "codemode-lsp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
Uzak URL mi, yoksa makinenizde bir komut mu? İki kurulum arasındaki fark
PlugMCP’de çalıştır
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
BaşlatYayıncıdan
Semantic code intelligence and refactoring for TypeScript/JavaScript agents:
an MCP server exposing a single execute tool backed by the language
server. The LLM writes one JavaScript script that chains semantic operations
(lsp.*) — filtering, looping, and aggregating in code instead of across many
tool-call round trips:
Semantic code intelligence + refactoring MCP for TypeScript/JS: one LSP-backed execute tool — call graphs, impact analysis, symbol dependencies, atomic multi-file refactors
const refs = await lsp.findReferences("src/api.ts", "handleRequest");
const relevant = refs.filter((r) => r.context.includes("deprecated"));
for (const ref of relevant) {
await lsp.replaceSymbolBody(ref.file, ref.symbolPath, newImpl);
}
({ modified: relevant.length });
It shines on codebase-wide work that grep-based agents get subtly wrong: impact analysis, call graphs, usage audits, and atomic multi-file refactors. Names are resolved, not text-matched. Writes are transactional — nothing hits disk unless the whole script succeeds, and successful writes come back as reviewable unified diffs.
No install step — the package bundles its own typescript-language-server.
The workspace root is the directory the server is spawned from:
{
"mcpServers": {
"codemode-lsp": {
"command": "npx",
"args": ["-y", "codemode-lsp"]
}
}
}
Add "env": { "CODEMODE_READONLY": "1" } to try it on a repo it physically
cannot write to.
The tool returns { result, logs, changes }. Symbols are addressed as
(file, "MyClass/myMethod") pairs discovered via getSymbols. When a script
does something a cheaper call covers, the result (and logs) carries an
advisory [hint]. Full type definitions are embedded in the tool description
(generated from source); if a client truncates it, await lsp.help() returns
the complete reference and await lsp.docs("query") returns just the matching
op signatures, related types, and a worked example.
See PRD.md for the complete spec and decision log.
checkProject() is the
whole-project check. On files created mid-script, per-file "Cannot find
module" alias errors are tagged likelyFalsePositive: true —
checkProject() has no such false positives.getDependencies is syntactic; moveSymbol moves top-level symbols only.Reference.isWriteAccess is always false (not exposed over standard LSP).bun run check # typecheck + lint + all tests — run before declaring done
bun run generate:types # regenerate src/lsp-types.generated.ts after API changes
bun run eval # LLM benchmark: headless Claude Code, execute tool only
The tool description's worked examples run verbatim as golden tests, and every eval task's reference solution runs in the normal suite — neither can rot.
Semantic code intelligence + refactoring MCP for TypeScript/JS: one LSP-backed execute tool — call graphs, impact analysis, symbol dependencies, atomic multi-file refactors
{ "mcpServers": { "codemode-lsp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Araçlar
Henüz araç listesi yok. Uzak sunucular ilk sağlık kontrolünden sonra bir liste alır.
SSS
Bu sayfadan Cursor, Claude Desktop, Claude Code veya VS Code için stdio yapılandırmasını kopyalayın. PlugMCP proxy'sini değil, yayıncının kurulumunu kullanır.
Bu kayıtta gerekli bir ortam değişkeni listelenmiyor.
Codemode Lsp yerel olarak stdio üzerinden çalışır.
Son kontrol: 2026-11-15. Semantic code intelligence + refactoring MCP for TypeScript/JS: one LSP-backed execute tool — call graphs, impact analysis, symbol dependencies, atomic multi-file refactors