Skip to main content
Glama
rajnaveen344

LSP Tools MCP Server

by rajnaveen344
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to LSP Tools MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP keyword search

      alfaarghya
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables keyword search within files, returning matching lines with line numbers.
      1
      1
      -

    • MCP Server with File Search

      DIYORAP
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server providing file search and question tools for AI models. Enables keyword search in files with line numbers and integration with external chat services.
      297 npm
      MIT

    • Codex MCP Server

      hailangx
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for local repository indexing and code understanding, enabling semantic search, AST analysis, dependency tracking, and symbol resolution.
      744 npm
      ISC

    • TokenScope

      cdgaete
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables token-aware directory exploration and file analysis for LLMs, helping them understand codebases through intelligent scanning and reporting.
      4
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes with no overlap. find_regex_position performs a specific text search operation on files, while list_allowed_directories provides metadata about server permissions. An agent would never confuse these tools as they serve fundamentally different functions in the workflow.

    Naming Consistency4/5

    Both tools follow a clear verb_noun naming pattern (find_regex_position, list_allowed_directories) with consistent snake_case formatting. The naming is logical and predictable, though with only two tools it's difficult to assess full consistency across a larger set.

    Tool Count2/5

    With only 2 tools, this server feels severely underpowered for an LSP (Language Server Protocol) context. LSP servers typically handle numerous language operations like diagnostics, completions, definitions, and references. This minimal toolset suggests either an incomplete implementation or a very narrow specialization that doesn't match typical LSP expectations.

    Completeness2/5

    For an LSP server, this toolset is severely incomplete. While the two provided tools are useful (file search and directory listing), they represent only a tiny fraction of expected LSP functionality. Missing are core language features like code completion, hover information, go-to-definition, references, diagnostics, formatting, and other standard LSP capabilities that agents would expect from such a server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources