Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
repowise earned a place on the map:
How we mapped it:
- alternative to
tokensave — Both are code-intelligence MCP servers that cut agent context burn; tokensave answers structural questions (symbols, callers, impact) from a semantic graph, repowise layers health scoring and executable refactoring plans on top of its own graph.
- alternative to
codegraph-mcp — Both serve a code knowledge graph to agents over MCP; codegraph-mcp goes deep on cross-language symbol/call/blast-radius queries, repowise trades some of that depth for defect-risk scores and refactoring plans.
If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.
Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
repowise earned a place on the map:
How we mapped it:
tokensave— Both are code-intelligence MCP servers that cut agent context burn; tokensave answers structural questions (symbols, callers, impact) from a semantic graph, repowise layers health scoring and executable refactoring plans on top of its own graph.codegraph-mcp— Both serve a code knowledge graph to agents over MCP; codegraph-mcp goes deep on cross-language symbol/call/blast-radius queries, repowise trades some of that depth for defect-risk scores and refactoring plans.If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.