MCP servers · bashbop

Solumbe: local repository context and merge-readiness gate for AI agents

A local, deterministic MCP server that builds repository context, scores how much a change touches, and gates merge readiness for AI-assisted development.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

Solumbe is a local-first trust layer that runs beside agent tools such as Claude Code, Codex, Cursor and Gemini rather than replacing them. Before an agent edits, it builds task-aware context showing which files, tests and commands a request needs. After the edit, it scores how far the diff departs from the stated intent and produces a receipt tied to the exact staged tree. Its gate returns PASS, WARN or FAIL, and it can flag any changed file that was never declared in advance. It runs with no server, no account, and no code leaving the machine, and its MCP server exposes 14 tools.

It suits teams that want a repeatable check on AI-generated changes before merging, and that want context regenerated from the actual code instead of hand-written notes. Its documentation compares it with hosted code search, with hand-maintained CLAUDE.md files, and with grep, noting that it ranks whole files by task intent and returns a context packet rather than a list of matching lines.

Installing runs a command that connects the MCP server to every detected agent host, with options to preview the plan or name specific hosts. Each host must be restarted afterwards. Every command accepts --json output. Optional hosted components exist, but nothing hosted is required, and the documentation lists what those components send and where.

Limitations and requirements

A passing local gate is not an automatic merge approval: hosted CI, GitHub review, CODEOWNERS and the human release decision remain separate authorities. Each agent host must be restarted after installation. Optional hosted components send data outside the machine, although none is required.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 15 Nov 2026 · its page on the source
    Solumbe

    Deterministic local repository context, impact analysis, and merge-readiness evidence for AI agents.

    v4.12.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026