Skip to main content
Glama
foldwork-dev

mcp-injector

by foldwork-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to mcp-injector

No user-submitted related servers found.

    Related Servers

    • Ambiance MCP Server

      sbarron
      A
      license
      A
      quality
      D
      maintenance
      Provides intelligent code context and analysis through semantic compression, AST parsing, and multi-language support. Offers 60-80% token reduction while enabling AI assistants to understand codebases through local analysis, OpenAI-enhanced insights, and GitHub repository integration.
      6
      31 npm
      3
      MIT

    • Headless Codebase Indexer

      y1hanh
      F
      license
      Not graded
      quality
      D
      maintenance
      A minimalist indexing tool that provides AI agents with semantic search and structural AST parsing for deep codebase understanding. It enables autonomous agents to navigate large codebases predictably using vector embeddings and native language server capabilities like definition and reference tracking.
      -

    • PureContext MCP

      goranocokoljic
      A
      license
      Not graded
      quality
      B
      maintenance
      Indexes codebases and lets AI agents retrieve precise code snippets (functions, classes, routes) instead of reading entire files, reducing token usage and improving accuracy.
      69 npm
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: get_project_map provides structural overview, injector_blast_radius analyzes dependencies, injector_diagram generates sequence diagrams, injector_inspect_table inspects database schemas, injector_regex_search performs fallback searches, and injector_write_file writes files. No overlap or ambiguity.

    Naming Consistency2/5

    Naming is inconsistent: get_project_map lacks the 'injector_' prefix used by the other five tools. The patterns after the prefix also vary: 'blast_radius' (noun phrase), 'diagram' (simple noun), 'inspect_table' (verb_noun), 'regex_search' (noun_noun), 'write_file' (verb_noun). No single convention is followed.

    Tool Count5/5

    With 6 tools, the server covers essential operations for a code injection and analysis tool: overview, dependency analysis, visualization, database inspection, search, and file writing. The count is well-scoped and appropriate for the domain.

    Completeness3/5

    The tool set covers reading (get_project_map), analysis (blast_radius, diagram), search (regex_search), and writing (write_file), but lacks partial file editing or incremental updates. The description emphasizes using injector_write_file for all edits, yet it only supports full file writes, leaving a notable gap for typical editing tasks.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources