lsp-tools-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@lsp-tools-mcpShow diagnostics for src/index.ts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
lsp-tools-mcp
Standalone Language Server Protocol tools exposed as a stdio MCP server.
Used By
This package is the upstream source of truth for two downstream plugins. Codex consumes the repository-level package directly; OpenCode consumes the same runtime as a built-in MCP package.
Project | Path | Role |
| Codex plugin that reuses these LSP MCP tools plus a Codex-specific PostToolUse diagnostics hook. | |
oh-my-openagent (a.k.a. |
| OpenCode plugin that registers this server as a built-in Tier-1 stdio MCP. Exposes |
If you fix or extend the LSP runtime here, downstream adapters should reuse this package. Do not fork the runtime into a downstream; land changes here instead.
Related MCP server: Codex LSP Bridge
Quick Start
npm install
npm run check
npm test
npm run build
printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | node dist/cli.js mcpMCP Tools
This server exposes the following tools:
lsp.statuslsp.diagnosticslsp.goto_definitionlsp.find_referenceslsp.symbolslsp.prepare_renamelsp.rename
Tool aliases are also available for compatibility:
lsp_statuslsp_diagnosticslsp_goto_definitionlsp_find_referenceslsp_symbolslsp_prepare_renamelsp_rename
When an MCP host registers this server under the name lsp (the default in both downstreams), the tools are exposed to agents as lsp_status, lsp_diagnostics, and so on, matching the alias names above.
Configuration
Default config paths (matches codex-lsp's historical layout):
Project:
.codex/lsp-client.jsonUser:
~/.codex/lsp-client.json
Path overrides via environment variables:
LSP_TOOLS_MCP_PROJECT_CONFIGLSP_TOOLS_MCP_USER_CONFIG
Examples (oh-my-openagent points the project config at .opencode/lsp.json via the env var):
LSP_TOOLS_MCP_PROJECT_CONFIG=.opencode/lsp.json node dist/cli.js mcp
LSP_TOOLS_MCP_USER_CONFIG=.opencode/lsp.json node dist/cli.js mcpExample config file:
{
"lsp": {
"typescript": {
"command": ["typescript-language-server", "--stdio"],
"extensions": [".ts", ".tsx", ".js", ".jsx"]
}
}
}Architecture
src/lsp/*standalone LSP runtime (process management, JSON-RPC transport, configuration, diagnostics, workspace edits)src/tools.tsMCP tool definitions and handlerssrc/mcp.tsstdio MCP server entry and registrationsrc/cli.tsstandalone CLI entry (mcpsubcommand only)
Local Development
npm install
npm run check
npm test
npm pack --dry-runLicense
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/code-yeongyu/lsp-tools-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server