Skip to main content
Glama
AvaTar-ArTs

Ecosystem Intelligence MCP

by AvaTar-ArTs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Ecosystem Intelligence MCP

No user-submitted related servers found.

    Related Servers

    • LocalFS MCP Server

      mcp-bridge
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides sandboxed access to local filesystem operations including directory and file management, content search with glob and regex patterns, and binary file support with configurable safety limits.
      -

    • Context MCP

      geq1fan
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with secure, read-only file system access to analyze and understand project codebases, enabling multi-repository context aggregation and cross-project code tracing.
      5
      MIT

    • Local Code MCP Server

      udittripathi
      F
      license
      B
      quality
      D
      maintenance
      Provides LLMs with safe, read-only access to local codebases for searching, reading files, and finding function definitions. All source code remains local, ensuring privacy while enabling AI assistants to explore project structures and functionality.
      4
      -

    • MCP Workspace Server

      ShayYeffet
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides secure, sandboxed file system access for AI assistants to read, write, and manage project files with controlled command execution capabilities, all confined to a designated workspace directory.
      MIT

    • codescope

      ellugia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only, allowlisted filesystem and Git inspection of explicitly configured local repositories through MCP, with bounded reads and no arbitrary path or write access.
      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

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing roots, summarizing projects, reading files, and analyzing project purpose. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the consistent verb_noun pattern in snake_case (inventory_roots, summarize_project, read_project_file, analyze_project). This makes the API predictable and easy to navigate.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped to its purpose of inspecting and analyzing projects. Each tool is essential and there is no bloat.

    Completeness5/5

    The tool surface covers the full workflow: discover roots, summarize structure, read specific files, and derive an analysis. No obvious missing operations for the stated domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources