Github MCP Server vs Repowise

A side-by-side look at the Github MCP Server and Repowise MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Github MCP Server logoGithub MCP ServerVersion ControlAI-optimized GitHub MCP server: 112 tools, 98% token reduction, compact responses.33EmergingAuth: not declaredRepowise logoRepowiseVersion Control · Local subprocess (stdio)Codebase intelligence for AI coding agents. Indexes a repo into a dependency graph, git history, defect-risk code health, auto-generated docs, and architectural decisions, served as 9 task-shaped MCP tools across 15 languages. Runs 100% local; hosted option available.61GoodAuth: no auth required

Verdict: choose Github MCP Server for version control work; choose Repowise for version control as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Github MCP Server logoChoose Github MCP Server when

  • You need dedicated capabilities in the Version Control domain.
Explore Github MCP Server

Repowise logoChoose Repowise when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Repowise

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGithub MCP Server logoGithub MCP ServerRepowise logoRepowise
CategoryVersion ControlVersion Control
Quality signal33/100 · Emerging61/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars57,891
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Github MCP Server tools

No tool names declared yet. Check the project README from the listing page.

Repowise tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Github MCP Server

No confirmed install command for Github MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.

Repowise

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "repowise-dev-repowise": {
      "command": "uvx",
      "args": [
        "repowise"
      ]
    }
  }
}

Frequently asked questions

Github MCP Server is categorized under Version Control and uses an install path we have not confirmed yet. Repowise belongs to Version Control and uses a local stdio subprocess. Pick Github MCP Server for version control work and Repowise for version control.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Github MCP Server has no confirmed install command yet — follow its own setup instructions.

Github MCP Server has no declared pricing — check the project's own site. Repowise is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add github-mcp-server-2 and repowise-dev-repowise as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Github MCP Server has a quality signal of 33/100 (Emerging) with 1 views, 0 installs and 5 GitHub stars. Repowise has 61/100 (Good) with 5 views, 0 installs and 7,891 GitHub stars.