Skip to main content
Glama
repowise-dev

repowise

by repowise-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to repowise

Related Servers

  • CodeGraph

    Phoenixrr2113
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to search code by meaning, explore codebase structure, store and query knowledge with temporal facts, and read source code through a set of MCP tools.
    267 npm
    7
    MIT

  • OpenCodeHub MCP Server

    laithalsaadoon
    A
    license
    Not graded
    quality
    A
    maintenance
    Provides code intelligence for AI coding agents by indexing repositories into a hybrid knowledge graph, enabling agents to query dependencies, impact, and context through 28 MCP tools.
    3
    Apache 2.0

  • codegraph

    optave
    A
    license
    Not graded
    quality
    A
    maintenance
    Provides AI agents with a function-level dependency graph of the codebase through 30 MCP tools, enabling structural queries about code dependencies, callers, and impact analysis.
    1,555 npm
    95
    Apache 2.0

  • codecortex

    rushikeshmore
    A
    license
    Not graded
    quality
    D
    maintenance
    Persistent codebase knowledge layer for AI agents. Pre-digests codebases into structured knowledge (symbols, dependency graphs, co-change patterns, architectural decisions) and serves via MCP. 28 languages, 14 tools, ~85% token reduction.
    12 npm
    8
    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.6/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct analytical concern: health scores, change risk, context triage, decision rationale, question answering, dead code, overview, history risk, symbol bodies, and raw search. Where overlap exists (get_answer vs get_why vs search_codebase, get_health vs get_risk), the descriptions explicitly carve out boundaries and direct callers to the right tool.

Naming Consistency4/5

Nine of ten tools follow a consistent get_<subject> pattern, making the set predictable and easy to navigate. search_codebase breaks the pattern slightly, though it is still readable and uses a clear verb-object structure.

Tool Count5/5

Ten tools is well-scoped for a code intelligence and health analysis server. Each tool covers a distinct capability with no obvious redundancy, and the count is squarely in the comfortable range for an MCP server.

Completeness5/5

The surface covers the full read-only exploration lifecycle: orient with get_overview, search with search_codebase, answer questions with get_answer, drill into context/symbols, assess health/risk/dead code, and understand rationale with get_why. There are no obvious dead ends, and the tools are designed to chain together coherently.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources