Skip to main content
Glama
Sign In
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.
    348 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,803 npm
    99
    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.
    3 npm
    10
    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.2/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct purposes, but there are a few subtle overlaps: get_answer also handles why questions that get_why specializes in, and get_context can return symbol-level information while get_symbol is the dedicated symbol reader. The descriptions explicitly clarify these boundaries, so misselection is possible but not likely.

Naming Consistency4/5

Nine of ten tools follow the get_<noun> pattern in snake_case, which is highly predictable. search_codebase is the only deviation, but it remains readable and clearly action-oriented.

Tool Count5/5

Ten tools is well-scoped for a repository intelligence server. Each tool covers a distinct analysis need, and there is no obvious padding or missing core capability.

Completeness4/5

The surface covers orientation, search, Q&A, context, symbol reading, risk, change risk, health, dead code, and decision archaeology, which is a strong lifecycle for codebase understanding. Minor gaps remain around explicit repository listing or analysis refresh, but agents can work around these via existing parameters and external commands.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources