Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Celmis

by Celmis-labsversion 0.1.30i★ –iRuns on your computer
Registry nameio.github.constantinemakoid/celmis

Install

Overview

Description from the maker (original English)

Self-hosted code intelligence: cross-repo Q&A, dependency audits and PR review, over MCP

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 0 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

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.30

Open in Cursor

Or copy the settings yourself

Paste 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.

Open in VS Code

Or copy the settings yourself

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.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ! Caution

    Maker matches the repo

    The publisher (constantinemakoid) is not the repo owner (Celmis-labs); someone else may have listed it

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32489 servers in this category
  • Published to the registry more recently than 43% of the other 32489 servers in this category
  • Basic checks equal to or better than 33% of the other 32489 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Celmis safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.30) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Whisper

Alternatives

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Whisper

by whisper-sec

One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.

Computer or cloudUpdated today
Install

README from the maker

Open the README

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.

Celmis

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:

  • understand code nobody documented: questions across repositories answered with 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;
  • review pull requests with what the change touches beyond its own repository;
  • secure the dependencies: CVE audit, a CycloneDX SBOM and an evidence pack a third party can verify;
  • fix what an alert or a finding points at: an embedded Claude Code session on *your* subscription edits the code and the runner opens a pull request (220 seconds on one measured finding). A person reviews and merges; Celmis never merges or deploys.

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.

What it does

Ask the codeQuestions across several repositories, answered with file:line citations on both sides of a call. Ask the code
Codebase and MCP51 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 reviewAgents 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
EvidenceDependency audit, CycloneDX SBOM and an evidence pack whose manifest a third party recomputes. SBOM and evidence
Fix from hereAn 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 defendRepositories 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

Install

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.

What's new in v3

  • Review that earns its comments. Findings below your comment level never reach the pull request; a review with nothing to say approves. Comments are the problem, the reason and the fix, in the repository's language (3.1).
  • A reviewer you can talk to. @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).
  • Knowledge packs. Versioned skills, API examples and checklists per workspace, readable in the app and by coding assistants through brief and skills; celmis-pack publishes them (3.0).
  • Access closed by default. A repository nobody has a rule for is invisible; MCP tokens belong to a person; every call is audited (2.3.7). Stricter secret hiding in 3.0.2.
  • Sharing between workspaces. For research, for a fixed time, with hidden paths and a ceiling on readers (3.1).
  • A developer MCP profile and a Claude Code plugin sized for an editor (2.3.7).

Every release is in the changelog.

Logs, and where the line falls

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.

What that buys you that a diff-only tool cannot

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.


Nine things people do with it

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 worksAsk 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 answerEvery 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 repositoryLoad 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 SBOMOne 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 reviewingAgents 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 themWrite 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 deskIt 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 codebasePoint 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.

Three numbers

197 secondsfrom git clone to six healthy services, measured on a clean server
$0.118per pull request reviewed, on the model this ships with
17th of 50on 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.

Table of contents

  • What it does
  • What's new in v3
  • What that buys you that a diff-only tool cannot
  • Nine things people do with it
  • Three numbers
  • Quick start
  • First user and admin
  • Connect a repository
  • Ask the code
  • Pull-request review
  • Dependencies, SBOM and the evidence pack
  • Fix from here
  • Alerts, and fixing from a phone
  • Ask for work across repositories
  • Who can see what
  • Languages and formats
  • Deterministic checks — no model, no false positives
  • Connect Claude Code and other MCP clients
  • Results
  • Audit of the false positives
  • Test repositories
  • Configuration
  • Operations
  • Local development
  • CLI reference
  • Architecture
  • Troubleshooting
  • Project layout
  • Provenance and rights

Quick start

What you need
Docker24+ with Compose v2Docker Desktop on macOS/Windows, the native engine on Linux
A model API keyone ofGoogle Gemini, Anthropic, OpenAI, OpenRouter, Groq or Mistral. A free Gemini key is enough to evaluate: https://aistudio.google.com/app/apikey
RAM~4 GB freeMeasured 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

Ask PopNx