language-server-mcp MCP Server

Created By
alexwohletza year ago
Overview

what is language-server-mcp?

language-server-mcp is a Model Context Protocol (MCP) server designed to enhance code editing experiences by providing language support features such as hover information, code completion, and diagnostics for TypeScript, with theoretical support for other languages like Python.

how to use language-server-mcp?

To use language-server-mcp, you need to install the dependencies, build the server, and configure it with your code editor (e.g., Claude Desktop) by specifying the server path in the appropriate config file.

key features of language-server-mcp?

  • Language-specific support for TypeScript with hover information, code completion, and diagnostics.
  • Implements the MCP protocol for effective communication with clients.
  • Tools for retrieving hover info, completion suggestions, and diagnostics via specified parameters.

use cases of language-server-mcp?

  1. Enhancing TypeScript code editing with real-time diagnostics and code suggestions.
  2. Providing language analysis features for improved code quality management.
  3. Integrating with other tools that support the MCP for extended language functionality.

FAQ from language-server-mcp?

  • What programming languages does language-server-mcp support?

Currently, it supports TypeScript and is theoretically capable of supporting Python, with plans to expand language functionality.

  • How do I install language-server-mcp?

Install dependencies using npm install, then build the server with npm run build, and configure your editor accordingly.

  • How can I debug language-server-mcp?

Use the MCP Inspector for debugging, which provides a URL to access debugging tools in your browser.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
alexwohletz
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

11 hours ago