What is the key difference between Shebe and Fossick?

Shebe belongs to the Version Control category with cloud HTTP/SSE execution, while Fossick belongs to the Version Control category with local stdio execution.

How do I install Shebe or Fossick in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Shebe and Fossick free or paid?

Shebe operates under a Free / Open Source model (No auth required). Fossick operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Shebe lists 0 tools with 0 views and 0 GitHub stars. Fossick lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Shebe and Fossick together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Shebe or Fossick in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Shebe and Fossick free to use, or do they require API keys?

Shebe is listed under a Free / Open Source model with No auth required . Fossick operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Shebe and Fossick at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both shebe and fossick as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Shebe has a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars. Fossick holds a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Shebe vs Fossick

In-depth architectural comparison of the Shebe and Fossick MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Shebe

Version Control · Remote HTTP/SSE

Quality: 42/100 (Fair) | Auth: No auth required

Fossick

Version Control · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Shebe if you need specialized Version Control tools running via a hosted cloud SSE transport. Choose Fossick if your workspace requires Version Control integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Shebe when:

You need dedicated capabilities in the Version Control domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Shebe Details

Choose Fossick when:

You need dedicated capabilities in the Version Control domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Fossick Details

Feature & Specification Comparison

Specification	S Shebe Version Control	F Fossick Version Control
Summary	Fast BM25 full-text search for code repositories. 14 MCP tools, 2ms search latency.	Search all of GitHub from your AI agent — find libraries, drill into repos, find code patterns.
Category & Scope	Version Control	Version Control
Quality signal

Tools & Capabilities Breakdown

Shebe Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Fossick Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Shebe Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "shebe": {
      "url": "https://gitlab.com/rhobimd-oss/shebe"
    }
  }
}

Fossick Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "fossick": {
      "command": "npx",
      "args": [
        "-y",
        "fossick"
      ]
    }
  }
}

Frequently Asked Questions

Shebe is categorized under Version Control and uses a remote streaming HTTP/SSE transport. In contrast, Fossick belongs to Version Control using local stdio subprocess. Select Shebe when you need capabilities focused on version control and Fossick when you require tools for version control.

More alternatives to Shebe More alternatives to Fossick Version Control category hub Canonical compare URL

Related MCP Server Comparisons

Popular comparisons with Shebe

Popular comparisons with Fossick

G
Fossick vs Github Mcp Server