{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm-cclsp","slug":"cclsp","name":"cclsp","type":"mcp","url":"https://github.com/ktnyt/cclsp#readme","page_url":"https://unfragile.ai/cclsp","categories":["mcp-servers"],"tags":["mcp","lsp","language-server","model-context-protocol","claude-code"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm-cclsp__cap_0","uri":"capability://tool.use.integration.language.server.protocol.bridging.via.mcp","name":"language server protocol bridging via mcp","description":"Exposes Language Server Protocol (LSP) capabilities through the Model Context Protocol (MCP) interface, allowing Claude and other MCP clients to invoke LSP operations (diagnostics, completions, definitions, references) on any language with an LSP implementation. Acts as a protocol adapter that translates MCP tool calls into LSP JSON-RPC messages and streams responses back through the MCP transport layer.","intents":["I want Claude to understand code structure and semantics using the same LSP servers my IDE uses","I need to give Claude access to language-specific analysis without reimplementing language intelligence","I want to leverage existing LSP implementations (Pylance, TypeScript, Rust Analyzer) in AI workflows"],"best_for":["AI engineers building code-aware agents that need semantic understanding beyond regex/AST parsing","Teams wanting to unify LSP tooling across IDE and AI-powered development workflows","Developers integrating Claude Code with existing LSP-based development environments"],"limitations":["Requires a running LSP server instance per language — no built-in server lifecycle management","LSP server startup and initialization latency (typically 1-5 seconds per language) adds overhead to first request","No caching of LSP responses — each MCP request triggers a fresh LSP query, potentially expensive for large codebases","Limited to LSP capabilities exposed by the underlying server; some servers have incomplete implementations"],"requires":["Node.js 16+ (for MCP server runtime)","At least one LSP server binary installed and accessible in PATH or via explicit configuration","MCP client implementation (e.g., Claude Desktop, custom MCP client)","Network connectivity or local socket access to LSP server process"],"input_types":["file paths (string)","line/column positions (integers)","code text (string)","LSP method names (string identifiers)"],"output_types":["structured LSP responses (JSON)","diagnostic information (errors, warnings, hints)","code completions (CompletionItem arrays)","symbol definitions and references (Location arrays)"],"categories":["tool-use-integration","code-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-cclsp__cap_1","uri":"capability://code.generation.editing.multi.language.semantic.code.completion.via.lsp","name":"multi-language semantic code completion via lsp","description":"Provides context-aware code completions by delegating to LSP servers' completion handlers, which perform semantic analysis on the codebase to suggest completions based on type information, scope, and available symbols. Translates MCP completion requests into LSP textDocument/completion calls, processes CompletionItem responses, and returns ranked suggestions with documentation and type hints.","intents":["I want Claude to suggest code completions that respect the language's type system and available APIs","I need completions that understand the current scope and imported modules, not just string matching","I want to use the same completion engine in Claude that my IDE uses"],"best_for":["Code generation agents that need to produce syntactically and semantically correct code","IDE-integrated AI assistants that must match IDE completion behavior","Polyglot development environments where multiple languages need consistent completion quality"],"limitations":["Completion quality depends entirely on LSP server implementation — some servers have incomplete or slow completion handlers","No deduplication or ranking across multiple LSP servers if multiple languages are active","Completion context limited to what LSP server can infer from current file and workspace — may miss cross-workspace dependencies","LSP completion can be slow for large projects (500ms-2s latency) due to symbol indexing"],"requires":["LSP server with textDocument/completion capability","File must be open in LSP server (requires prior didOpen notification)","Valid line and character position within the file"],"input_types":["file URI (string)","line number (integer, 0-indexed)","character position (integer, 0-indexed)","optional completion context (trigger character, incomplete token)"],"output_types":["CompletionItem array (label, kind, detail, documentation, sortText)","completion range (where to replace text)","optional resolve data for lazy-loaded details"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-cclsp__cap_2","uri":"capability://code.generation.editing.codebase.aware.symbol.definition.and.reference.lookup","name":"codebase-aware symbol definition and reference lookup","description":"Enables Claude to navigate code structure by querying LSP servers for symbol definitions and all references to a symbol across the codebase. Translates MCP requests into LSP textDocument/definition and textDocument/references calls, returning file locations and context for each match. Supports jump-to-definition workflows and impact analysis by identifying all usages of a symbol.","intents":["I want Claude to understand how a function or class is used throughout the codebase","I need to find all references to a symbol to assess refactoring impact","I want Claude to navigate to a symbol's definition to understand its implementation"],"best_for":["Code refactoring agents that need to identify all affected locations","Codebase navigation assistants that help developers understand code relationships","Impact analysis tools that assess the scope of changes"],"limitations":["Reference lookup can be slow on large codebases (1-5 seconds for popular symbols)","Some LSP servers have incomplete reference implementations or don't support cross-file references","Results limited to workspace scope — external dependencies may not be included","No deduplication of results if symbol is defined in multiple places (e.g., overloads)"],"requires":["LSP server with textDocument/definition and textDocument/references capability","File must be open in LSP server","Valid symbol position (line and character) pointing to an identifier"],"input_types":["file URI (string)","line number (integer, 0-indexed)","character position (integer, 0-indexed)"],"output_types":["Location array (file URI, range with start/end line and character)","optional context snippet for each location"],"categories":["code-generation-editing","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-cclsp__cap_3","uri":"capability://code.generation.editing.real.time.code.diagnostics.and.error.reporting","name":"real-time code diagnostics and error reporting","description":"Streams diagnostic information (errors, warnings, hints) from LSP servers as code is analyzed, translating LSP textDocument/publishDiagnostics notifications into MCP messages. Provides Claude with real-time feedback on code quality, type errors, linting violations, and other issues detected by the language server, enabling error-aware code generation and repair workflows.","intents":["I want Claude to see compilation errors and type mismatches as it generates code","I need Claude to understand linting violations and style issues in the codebase","I want Claude to fix errors by understanding what the language server reports"],"best_for":["Code generation agents that need to validate output against language semantics","Error-fixing assistants that repair code based on compiler/linter feedback","Development workflows where Claude needs to understand code quality issues"],"limitations":["Diagnostic accuracy depends on LSP server implementation — some servers have incomplete error detection","Diagnostics are asynchronous and may lag behind code changes by 100-500ms","No aggregation of diagnostics across multiple LSP servers if multiple languages are active","Some LSP servers don't publish diagnostics for all file types (e.g., only for open files)"],"requires":["LSP server with diagnostic capability (most servers support this)","File must be open in LSP server to receive diagnostics","MCP client must support streaming/notification messages"],"input_types":["file URI (string)","file content (string, sent via didChange notification)"],"output_types":["Diagnostic array (message, severity level, range, source, code)","optional related information (additional locations, fixes)"],"categories":["code-generation-editing","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-cclsp__cap_4","uri":"capability://search.retrieval.workspace.aware.file.and.symbol.indexing","name":"workspace-aware file and symbol indexing","description":"Manages LSP workspace initialization and maintains an index of files and symbols across the codebase by coordinating LSP workspace/didChangeWatchedFiles and workspace/symbol queries. Enables Claude to discover available symbols, modules, and files without scanning the filesystem, leveraging the LSP server's pre-built index for fast lookups and cross-file analysis.","intents":["I want Claude to know what symbols and modules are available in the codebase without scanning files","I need Claude to search for symbols by name across the entire workspace","I want Claude to understand the codebase structure and available APIs"],"best_for":["Code generation agents that need to discover available APIs and modules","Codebase exploration tools that help developers understand project structure","Refactoring tools that need to identify all symbols for renaming or reorganization"],"limitations":["Workspace indexing can be slow on large projects (10-30 seconds for 100k+ files)","Symbol search results may be incomplete if LSP server doesn't index all file types","No incremental updates — workspace must be re-indexed if files are added/removed outside LSP client","Symbol search is case-sensitive in some LSP servers, limiting fuzzy matching"],"requires":["LSP server with workspace/symbol capability","Workspace root directory configured in LSP initialization","File watcher support (workspace/didChangeWatchedFiles) for dynamic updates"],"input_types":["workspace root path (string)","symbol query string (for workspace/symbol searches)"],"output_types":["SymbolInformation array (name, kind, location, container name)","optional file list with metadata"],"categories":["search-retrieval","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-cclsp__cap_5","uri":"capability://tool.use.integration.multi.lsp.server.orchestration.and.lifecycle.management","name":"multi-lsp server orchestration and lifecycle management","description":"Manages multiple LSP server instances for different languages within a single MCP server process, handling server initialization, shutdown, and request routing based on file type. Implements LSP client protocol to spawn and communicate with language servers, maintaining separate connections and state for each language while exposing a unified MCP interface.","intents":["I want Claude to work with multiple programming languages in the same codebase using their respective LSP servers","I need to manage LSP server lifecycle (startup, shutdown, restart) automatically","I want to route requests to the correct LSP server based on file type"],"best_for":["Polyglot development teams working with multiple languages in one project","AI agents that need to analyze and generate code across different languages","Development environments where different languages require different semantic analysis"],"limitations":["Each LSP server consumes memory and CPU — managing many servers simultaneously can be resource-intensive","No built-in load balancing or connection pooling — each server is a separate process","Server startup latency multiplies with number of languages (e.g., 5 languages = 5-25 seconds startup)","No automatic server restart on crash — requires external monitoring or manual intervention"],"requires":["Node.js 16+ with child_process capability","LSP server binaries for each language installed and in PATH","Configuration file or environment variables specifying language-to-server mappings"],"input_types":["file URI with language/extension (string)","language identifier (string, e.g., 'python', 'typescript')"],"output_types":["routed LSP responses from appropriate server","server status information (running, initialized, error)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-cclsp__cap_6","uri":"capability://tool.use.integration.lsp.protocol.translation.and.mcp.integration","name":"lsp protocol translation and mcp integration","description":"Translates between LSP JSON-RPC protocol and MCP tool/resource interfaces, converting MCP tool calls into LSP method invocations and mapping LSP responses back to MCP format. Handles protocol differences (LSP's notification-based diagnostics vs MCP's request-response model) and manages state synchronization between the two protocols.","intents":["I want Claude to invoke LSP operations through standard MCP tool calls","I need LSP responses formatted as MCP tool results that Claude can understand","I want to abstract away LSP protocol complexity from the MCP client"],"best_for":["MCP client developers who want to use LSP capabilities without learning LSP protocol details","Teams integrating LSP into AI workflows via MCP","Developers building Claude Code extensions that need semantic code analysis"],"limitations":["Protocol translation adds ~50-100ms latency per request due to serialization/deserialization","Some LSP features (e.g., streaming responses) don't map cleanly to MCP's request-response model","Error handling differences between protocols may cause information loss in edge cases","No built-in versioning — breaking changes in LSP or MCP protocol require manual updates"],"requires":["MCP server implementation (Node.js with @modelcontextprotocol/sdk or equivalent)","LSP client library (e.g., vscode-languageclient) or custom JSON-RPC implementation","Protocol specification knowledge for both LSP and MCP"],"input_types":["MCP tool call with arguments (JSON)","LSP method name and parameters (string + JSON)"],"output_types":["MCP tool result (JSON)","LSP JSON-RPC response (JSON)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":39,"verified":false,"data_access_risk":"high","permissions":["Node.js 16+ (for MCP server runtime)","At least one LSP server binary installed and accessible in PATH or via explicit configuration","MCP client implementation (e.g., Claude Desktop, custom MCP client)","Network connectivity or local socket access to LSP server process","LSP server with textDocument/completion capability","File must be open in LSP server (requires prior didOpen notification)","Valid line and character position within the file","LSP server with textDocument/definition and textDocument/references capability","File must be open in LSP server","Valid symbol position (line and character) pointing to an identifier"],"failure_modes":["Requires a running LSP server instance per language — no built-in server lifecycle management","LSP server startup and initialization latency (typically 1-5 seconds per language) adds overhead to first request","No caching of LSP responses — each MCP request triggers a fresh LSP query, potentially expensive for large codebases","Limited to LSP capabilities exposed by the underlying server; some servers have incomplete implementations","Completion quality depends entirely on LSP server implementation — some servers have incomplete or slow completion handlers","No deduplication or ranking across multiple LSP servers if multiple languages are active","Completion context limited to what LSP server can infer from current file and workspace — may miss cross-workspace dependencies","LSP completion can be slow for large projects (500ms-2s latency) due to symbol indexing","Reference lookup can be slow on large codebases (1-5 seconds for popular symbols)","Some LSP servers have incomplete reference implementations or don't support cross-file references","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.4530013211321174,"quality":0.24,"ecosystem":0.55,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.328Z","last_scraped_at":"2026-04-22T08:08:13.650Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":9204,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=cclsp","compare_url":"https://unfragile.ai/compare?artifact=cclsp"}},"signature":"kwQ9O6uRfk6EoHNqS/6/fwyHpY5vmfsorocdBw7wrEyfYO5whaZIRXRnlWF6LqAMV9ISADlgSvzYftMgRi9DDA==","signedAt":"2026-06-21T16:56:22.114Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/cclsp","artifact":"https://unfragile.ai/cclsp","verify":"https://unfragile.ai/api/v1/verify?slug=cclsp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}