Skip to main content
Glama

Related Servers

Alternatives to spm-search-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that indexes a repository locally and provides keyword, semantic, hybrid, and SQL search tools, enabling coding agents to answer questions about the codebase efficiently without reading files one by one.
      3
      114 npm
      32
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to search and access open-source code, documentation, and package information via a local MCP server.
      2,005 npm
      120
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to search an index of 22k+ MCP servers, agent skills and coding-agent plugins directly from chat, returning matches with stars, install commands and page links, plus trending repos and curated best-of topic lists. Read-only, no API key required, usable via a hosted HTTP endpoint or locally over stdio.
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that indexes reference repositories and provides tools for AI coding agents to retrieve lossless code context, enabling reasoning over codebases larger than the agent's context window.
      8
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI agents to search code, find files, and read files in a codebase at lightning speed using ripgrep.
      MIT

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct and non-overlapping purpose: search_swift_packages finds packages, get_package_readme fetches details for a specific package, and list_search_filters provides metadata about valid search parameters. There is no ambiguity about which tool to use for each task.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: search_swift_packages, get_package_readme, and list_search_filters. The naming is predictable and clearly indicates each tool's function.

    Tool Count4/5

    Three tools is appropriate for the server's purpose of searching and exploring Swift packages, covering search, detail retrieval, and filter discovery. However, it feels slightly minimal—adding a tool for getting package metadata or dependencies could enhance completeness.

    Completeness4/5

    The tools cover the core workflow of searching for Swift packages, viewing filters, and reading READMEs, with no dead ends. A minor gap exists in lacking direct access to package metadata like versions or dependencies, but agents can work around this using the provided tools effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues