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.
    386 npm
    7
    MIT

  • OpenCodeHub MCP Server

    laithalsaadoon
    A
    license
    Not graded
    quality
    C
    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.
    4
    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.
    2,570 npm
    98
    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.
    9 npm
    9
    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.3/5.0

Scored across 10 tools

Disambiguation4/5

The descriptions aggressively cross-reference each other (get_answer vs search_codebase, get_context vs get_symbol, get_risk vs get_change_risk), making boundaries explicit. The one soft spot is the trio get_health / get_risk / get_change_risk, which all sound like scoring tools even though the text carefully separates code-quality, git history, and diff review.

Naming Consistency5/5

Every tool is snake_case with a clear verb_noun shape (get_change_risk, get_health, get_overview, get_why, get_dead_code, search_codebase). The get_ prefix dominates and search_codebase is the only search_ verb, which is a natural exception rather than a deviation.

Tool Count5/5

Ten tools is well-scoped for a repo-intelligence server. Each tool maps to a distinct stage: orientation (get_overview), retrieval (search_codebase, get_answer), inspection (get_context, get_symbol), and analysis (get_health, get_risk, get_change_risk, get_dead_code, get_why), with no filler.

Completeness4/5

The surface covers the full read-only lifecycle of repo understanding: discovery, context, Q&A, rationale, health, risk, change review, dead-code cleanup, and symbol drill-down, with workspace/multi-repo handling in get_overview. Minor gaps exist (no explicit workspace/repo listing or config tooling), but every core analysis workflow has a path.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources