Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Self-hosted code intelligence: cross-repo Q&A, dependency audits and PR review, over MCP
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"celmis": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/celmis-labs/celmis-api:v0.1.30"
]
}
}
}Run this in your terminal
claude mcp add celmis -- docker run -i --rm ghcr.io/celmis-labs/celmis-api:v0.1.30Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"celmis": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/celmis-labs/celmis-api:v0.1.30"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"celmis": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/celmis-labs/celmis-api:v0.1.30"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The publisher (constantinemakoid) is not the repo owner (Celmis-labs); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.30) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Whisper
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Understand, review, secure and fix your code, in one self-hosted place. One machine. Your model, your network. The code never leaves the company.
Website · Documentation · Quick start · What's new · Results
Celmis puts everything an engineering team needs to work with its code in one place. It indexes all of your repositories once, into a symbol graph built without a model, and every tool reads that same index:
file:line citations, in the app or from a coding agent (Claude Code, Cursor, Codex) over MCP, plus the team's own skills and checklists for the task at hand;It is built for the team that ships the code and answers for it in production. Instead of a separate tool for each of those jobs, each with its own access rules and its own copy of your code, one installation holds them all. The aim is a small team that can run several products and the integrations between them.
What "beyond its own repository" means today. Before a merge, the review checks the other repositories for values the change removes that they still hardcode, for deploy files that point at the changed repository, and for code that calls a changed function by the same name, quoting both sides. These are checks, not a call graph between repositories; that graph is not built yet.
| Ask the code | Questions across several repositories, answered with file:line citations on both sides of a call. Ask the code |
| Codebase and MCP | 51 tools over MCP, a compact /mcp/dev profile for editors, a Claude Code plugin, and versioned knowledge packs of the skills your team already explains out loud. MCP · Packs |
| Pull-request review | Agents read the diff and, where the graph exists, who else calls what changed, across repositories. Talk to it with @celmis, teach it with remember, and it stays quiet when there is nothing to say. Review |
| Evidence | Dependency audit, CycloneDX SBOM and an evidence pack whose manifest a third party recomputes. SBOM and evidence |
| Fix from here | An alert or a dependency finding becomes an embedded session, then a branch, then a pull request. A human reviews and merges; Celmis never merges. Fix from here · Alerts |
| Access you can defend | Repositories are closed by default, MCP tokens are issued per person, every call is audited, secrets are withheld at the source, and a repository can be shared with another workspace for a fixed time. Who can see what · Sharing |
git clone https://github.com/Celmis-labs/Celmis.git celmis && cd celmis
./scripts/init-env.sh # writes .env and fills every secret docker compose --env-file .env up -d
Then open http://localhost and paste one model provider key under Settings → LLM Setup.
197 seconds from clone to six healthy services on a clean server. Postgres and Qdrant are bundled; about 4 GB of RAM. Details in Quick start. An installation without a licence admits up to five people; see Licensing.
@celmis commands and questions in the thread, remember rules, learning from what the team dismisses, incremental review of each push, Jira acceptance criteria checked in the summary (2.3).brief and skills; celmis-pack publishes them (3.0).Every release is in the changelog.
Celmis does not watch your services; Grafana or whatever you already run does that. The application ingests no logs of its own and starts from the alert. The repository ships an optional observability overlay (Prometheus, Loki, Promtail, Grafana) that does collect them, platform-wide rather than Celmis-only:
docker compose -f docker-compose.yml -f docker-compose.observability.yml up -d
Every port binds to 127.0.0.1 and is reached over an SSH tunnel, because Loki has no authentication. GRAFANA_ADMIN_PASSWORD is required.
Ask a question that spans two repositories, and the answer quotes both, as in the screenshot at the top of this page. That is not a search result. The gateway and the payments service are separate repositories with no shared code, and the answer traces the call chain between them — then notices, unprompted, that the Kafka topic name is hardcoded in both and that changing one silently breaks the other.
A reviewer that reads only the diff structurally cannot say that. It never had the other repository open.
| You are a PM, a delivery lead or the client and want to know what state a group of projects is in, or how something actually works | Ask it. From any device, anywhere, without booking time from an engineer and without a meeting whose only output is a paragraph → Ask the code |
| A new engineer has a question a senior would have to answer | Every one of those pulls someone experienced out of flow, at the moment they are already covering. The codebase answers instead, with file:line citations → Ask the code |
| Two teams share an integration and neither can read the other's repository | Load it, grant the right to ask, and deny the paths that must stay private. They get answers; the credentials are refused at the source → Who can see what |
| A customer or an auditor asks for your SBOM | One button, CycloneDX, plus an evidence pack whose manifest they recompute themselves — against a hash you publish where the pack is not → Dependencies, SBOM and the evidence pack |
| A vulnerability lands in a dependency | *Fix from here* hands an embedded session the repository, the package and the finding. It edits, the runner pushes a branch and opens a PR → Fix from here |
| A pull request needs reviewing | Agents read the diff — and, where the graph is built, who else calls what is being changed, including from another repository → Pull-request review |
| Forty services need the same thing done to them | Write the sentence. Celmis shows which repositories it resolves to and waits for a second press, rather than finding them among forty and pressing a button forty times → Ask for work across repositories |
| An alert fires at 02:00 and you are not at a desk | It lands in Celmis and goes out to the workspace's chat channel, and *Fix from here* opens a session already holding the alert. The runner opens the pull request → Alerts, and fixing from a phone |
| Your own agent or editor needs to understand the codebase | Point it at /mcp/. Fifty-one tools over the same index, thirty-five of them read-only, under the same access rules — no second copy of your code anywhere → Connect Claude Code and other MCP clients |
The first three are the ones a code-review tool does not do at all, and they are the reason this is a platform rather than a reviewer: index once, then read that index from whichever side of the work you are standing on.
| 197 seconds | from git clone to six healthy services, measured on a clean server |
| $0.118 | per pull request reviewed, on the model this ships with |
| 17th of 50 | on the Martian Code Review Bench offline set, under all three judges |
That last one is deliberately unflattering, and it stays. It measures one of the surfaces below — pull-request review on isolated single-repository PRs — and that set has no sibling service for a symbol to have consumers in, so the thing this product is built around is not in the number at all. The table, the audit of every finding it scored false, and the command that reproduces both are in Results.
| Docker | 24+ with Compose v2 | Docker Desktop on macOS/Windows, the native engine on Linux |
| A model API key | one of | Google Gemini, Anthropic, OpenAI, OpenRouter, Groq or Mistral. A free Gemini key is enough to evaluate: https://aistudio.google.com/app/apikey |
| RAM | ~4 GB free | Measured on a real indexing run: 1.1 GB peak across all five containers, 565 MB at rest |
Postgres and Qdrant are **bundled
Only the beginning is shown; read the rest in the repo