vue-ts-lsp
Provides code intelligence for JavaScript, including hover, definitions, references, diagnostics, and workspace symbols.
Provides type-aware code intelligence for TypeScript, including hover, definitions, references, diagnostics, and workspace symbols.
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., "@vue-ts-lspShow me the definition of theuseRouterfunction in my Vue file"
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.
vue-ts-lsp-mcp
Self-contained, type-aware code intelligence for TypeScript / JavaScript / Vue, exposed to
MCP clients (Claude Code) as tools. A fork of cclsp that
bundles its own language servers so it needs no global installs.
Why this fork
Addition | What it does |
Vendored language servers |
|
Working | Hover / definition / references / diagnostics inside |
Relative-path output | Tool results show project-relative paths (node_modules collapsed) instead of absolute paths. Root via |
MCP server instructions | The server advertises when/how to use each tool (prefer it over grep for symbol work), surfaced to the client on connect. |
Env-expanded config |
|
esbuild build | Node-native bundle ( |
Related MCP server: MCP-Typescribe
Install as a Claude Code plugin
The repo is a Claude plugin (.claude-plugin/plugin.json + .mcp.json). Point a local
marketplace at it and install, or add it directly. On install it registers an MCP server named
vue-ts-lsp (tools appear as mcp__vue-ts-lsp__*). Nothing else to set up — the language servers
are vendored. The distinct name avoids any clash with an upstream cclsp install. The server
advertises its own usage guidance (when to prefer it over grep) via MCP instructions on connect,
so no companion skill is required.
The MCP server is launched as:
// .mcp.json
{
"vue-ts-lsp": {
"command": "node",
"args": ["${CLAUDE_PLUGIN_ROOT}/dist/index.js"],
"env": {
"CCLSP_CONFIG_PATH": "${CLAUDE_PLUGIN_ROOT}/cclsp.json",
"CCLSP_PLUGIN_ROOT": "${CLAUDE_PLUGIN_ROOT}"
}
}
}CCLSP_REL_ROOT is intentionally unset — paths relativize against the server's working directory
(your project root). Set it explicitly if your client launches the server elsewhere.
Tools
find_definition · find_references · find_implementation · find_workspace_symbols ·
get_hover · prepare_call_hierarchy · get_incoming_calls · get_outgoing_calls ·
get_diagnostics · rename_symbol · rename_symbol_strict · restart_server.
Routing guidance (which tool for which question, addressing, gotchas) is delivered to the client as
MCP server instructions on connect — see SERVER_INSTRUCTIONS in index.ts.
Develop
npm install # build deps (esbuild, typescript, MCP SDK) — root node_modules, NOT committed
npm run build # esbuild -> dist/index.js (commit dist/ so the plugin runs on install)
npm run typecheck # tsc --noEmit (production sources; bun:test files excluded)
node scripts/smoke.mjs # MCP handshake: initialize + tools/list + instructions
node scripts/integration.mjs # live TS + Vue checks against scripts/fixture.vue
npm run dev # esbuild --watchAfter editing src/, rebuild and commit dist/ — the committed bundle is what runs on install.
Updating the vendored language servers
cd vendor && npm install # bump versions in vendor/package.json firstSyncing upstream cclsp
upstream remote points at ktnyt/cclsp; origin is this fork. git fetch upstream then merge
as needed. Fork-specific changes live in src/lsp/adapters/ (vue + tsserver-bridge),
src/utils.ts (relpath), src/lsp/config.ts (env expansion), and index.ts (instructions).
License
This server cannot be installed
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
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/enc0ded/vue-ts-lsp-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server