Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
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.
AbrirDo publicador
Codex plugin that ports the standalone LSP runtime from pi-lsp-client. It gives Codex post-edit diagnostics plus explicit MCP tools for language-aware code work.
Codex plugin that exposes Language Server Protocol diagnostics and MCP tools
The LSP runtime moved to lsp-tools-mcp and is consumed here as a git submodule at packages/lsp-tools-mcp/.
codex-lsp keeps Codex-specific integration (hook post-tool-use, plugin metadata, package wiring).lsp-tools-mcp owns MCP runtime, LSP manager, and tool implementations.src/cli.ts routes mcp to upstream runtime and keeps hook post-tool-use local.Deletes are ignored because they cannot introduce new diagnostics.
lsp.statuslsp.diagnosticslsp.goto_definitionlsp.find_referenceslsp.symbolslsp.prepare_renamelsp.renamelsp.rename applies the returned workspace edit to files. Use lsp.prepare_rename first when possible.
Project config:
.codex/lsp-client.json
User config:
~/.codex/lsp-client.json
Example:
{
"lsp": {
"typescript": {
"command": ["typescript-language-server", "--stdio"],
"extensions": [".ts", ".tsx", ".js", ".jsx"]
}
}
}
Built-in server definitions are used when no custom config overrides them. lsp.status shows which configured servers are installed or missing.
The plugin ships:
.codex-plugin/plugin.json for Codex plugin discovery..mcp.json for the lsp MCP server.hooks/hooks.json for the PostToolUse diagnostics hook.skills/lsp/SKILL.md with MCP usage guidance.The runtime depends on @code-yeongyu/lsp-tools-mcp via file:./packages/lsp-tools-mcp, so marketplace builds must include submodule contents.
The hook command is:
node "${PLUGIN_ROOT}/dist/cli.js" hook post-tool-use
The MCP command is:
node ./packages/lsp-tools-mcp/dist/cli.js mcp
git submodule update --init --recursive
npm run bootstrap # installs + builds the lsp-tools-mcp submodule
npm install
npm test
npm run typecheck
npm run check
npm pack --dry-run
The bootstrap script installs and builds the lsp-tools-mcp git submodule so
@code-yeongyu/lsp-tools-mcp/dist/*.js is available for the codex-lsp build.
Smoke-test the hook:
node dist/cli.js hook post-tool-use < test/fixtures/post-tool-use.json
Smoke-test the MCP server:
printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | node dist/cli.js mcp
From the marketplace root containing this plugin:
codex plugin marketplace add /path/to/codex-plugins
node /path/to/codex-plugins/scripts/install-local.mjs /path/to/codex-plugins
If your local Codex build exposes plugin install commands, you can install from the UI or CLI instead. For older local builds, the marketplace installer builds and copies the plugin into ~/.codex/plugins/cache/<marketplace>/omo/0.1.0 and enables:
[plugins."omo@code-yeongyu-codex-plugins"]
enabled = true
main is protected by .github/branch-ruleset.json.v<semver>.publish workflow after a GitHub Release is published.This plugin runs locally. It starts configured language-server commands on your machine and does not call a network service by itself.
MIT.
Codex plugin that exposes Language Server Protocol diagnostics and MCP tools
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Codex Lsp roda localmente via stdio.
Última verificação: 2026-11-05. Codex plugin that exposes Language Server Protocol diagnostics and MCP tools
