接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令？ 兩種安裝方式的差異
來自發布者
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
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式，而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Codex Lsp 透過 stdio 在本機執行。
上次檢查時間：2026-11-05。 Codex plugin that exposes Language Server Protocol diagnostics and MCP tools
