TypeScript LSP plugin enabled but tools not available in session

Description

The TypeScript LSP plugin (typescript-lsp@claude-plugins-official) is enabled in settings but the MCP tools are not available during the Claude Code session.

Environment

• OS: Windows 11
• Claude Code version: Latest
• Node.js: v22.21.1
• typescript-language-server: v5.1.3 (installed globally via npm)

Configuration

In ~/.claude/settings.json:

"enabledPlugins": {
  "typescript-lsp@claude-plugins-official": true,
  // ... other plugins
}

The plugin files exist in:

• ~/.claude/plugins/cache/claude-plugins-official/typescript-lsp/1.0.0/
• ~/.claude/plugins/marketplaces/claude-plugins-official/plugins/typescript-lsp/

Expected Behavior

Claude should have access to mcp__plugin_typescript_lsp__* tools for:

• Go-to-definition
• Find references
• Error checking
• Other LSP features

Actual Behavior

No TypeScript LSP tools appear in the available tools list. Other plugins (supabase, playwright, context7, greptile) load correctly and their tools are available.

Steps to Reproduce

1. Install typescript-language-server globally: npm install -g typescript-language-server typescript
2. Enable the plugin in settings.json: "typescript-lsp@claude-plugins-official": true
3. Restart Claude Code
4. Check available tools - no mcp__plugin_typescript_lsp__* tools present

Additional Context

The plugin appears to fail silently - no error messages are shown during startup. Other LSP plugins (clangd-lsp, pyright-lsp, etc.) are also enabled but similarly don't appear to load their tools.