w3-mcp-server-lsp

Provides an MCP server (stdio) that wraps a TypeScript Language Server to offer LSP-backed code intelligence tools such as go-to-definition, hover, and find-references for JavaScript/TypeScript projects.

Evaluated Apr 04, 2026 (0d ago)

Homepage ↗ Repo ↗ DevTools mcp lsp typescript javascript code-intelligence python stdio

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Transport security for stdio is not applicable; README does not specify auth/authorization for the MCP server beyond a proxy token mentioned for the inspector URL. The server likely accesses local files under PROJECT_ROOT; ensure PROJECT_ROOT and file paths are controlled to avoid unintended filesystem exposure. Secret handling practices and logging redaction are not documented.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want to add LSP code intelligence to an MCP client for JavaScript/TypeScript and you can run the server locally with a properly configured project root.

Avoid When

You need documented authentication/authorization controls, strict rate-limit guarantees, or multi-tenant SaaS-style deployment constraints.

Use Cases

• IDE/agent-driven code navigation (definition, hover, references) for JS/TS codebases
• Integrating LSP capabilities into an MCP-compatible client (e.g., Claude Code)
• Interactive debugging/testing of MCP tools via an MCP inspector web UI

Not For

• Production-grade managed hosted service (appears to be a local developer tool/server)
• Non-JS/TS languages (e.g., Python, Go) without additional language server support
• Environments requiring a strict security model with fine-grained auth policies (not clearly specified)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: MCP proxy auth token (shown as MCP_PROXY_AUTH_TOKEN for the inspector URL)

OAuth: No Scopes: No

README references an inspector URL with MCP_PROXY_AUTH_TOKEN but does not define a full auth model for the MCP server itself (stdio mode appears local).

Pricing

Free tier: No

Requires CC: No

No pricing described; appears to be a library/tool distributed under MIT.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Tool inputs use 0-indexed line/character positions (off-by-one risk).
⚠ file_path is relative to PROJECT_ROOT; incorrect root/path will cause failures.
⚠ Requires typescript-language-server to be installed and discoverable on PATH (or configured via the install steps).

Alternatives

Direct TypeScript Language Server integration via an LSP client (without MCP) Other MCP servers that provide code intelligence for JS/TS (if available in your ecosystem) Use an IDE/editor with built-in TS language server integration

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for w3-mcp-server-lsp.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.