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

Karakoram

by KarakoramDevversion 0.4.3i★ –iRuns in the cloud
Registry nameio.github.KarakoramDev/karakoram

Install

Overview

Description from the maker (original English)

Self-hosted database control plane: clusters, backups and operations. Read-only by default.

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.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Databases & datasets
  • You need to fill in: Authorization

Install

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

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http karakoram 'https://{control_plane_host}/mcp' --header 'Authorization: Bearer {api_token}'

Fill in the empty values before running it.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "karakoram": {
      "url": "https://{control_plane_host}/mcp",
      "headers": {
        "Authorization": "Bearer {api_token}"
      }
    }
  }
}

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.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "karakoram": {
      "type": "http",
      "url": "https://{control_plane_host}/mcp",
      "headers": {
        "Authorization": "Bearer {api_token}"
      }
    }
  }
}

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 address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization secret required HTTP header
    Karakoram API token; `karactl mcp config` mints a restricted, read-only one

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The address needs your own values, so we cannot read the tool list for you.

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 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account KarakoramDev, which owns the repo

  • … 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

    The address needs your own account values, so we cannot check it for you

  • – Not applicable

    Sign-in with OAuth

    The address needs your own account values, so we cannot check it for you

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Databases & datasetsi

  • More stars than 0% of the other 955 servers in this category
  • Published to the registry more recently than 93% of the other 955 servers in this category
  • Basic checks equal to or better than 100% of the other 955 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 Karakoram safe?

It passed 1 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?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.3) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server

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

Supabase

by supabase

Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.

Computer or cloud★ 2,993Apache-2.0Updated yesterday
Install

MongoDB MCP Server

by mongodb-js

MongoDB Model Context Protocol Server

Runs on your computer★ 1,157Apache-2.0Updated 3 days ago
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.

Karakoram

Karakoram is a multi-platform, self-hosted control plane for database and stateful-service orchestration inside your infrastructure, without Kubernetes or a hosted coordinator. A Go control plane provides a REST API, karactl CLI and web UI; providers supply infrastructure, while you operate the installation, credentials, data and recovery procedures. Zerops is the reference provider; Karakoram's maintainer works at Zerops (see Acknowledgements). Dokploy and Nomad are also available; see Providers for their status.

Status: pre-1.0. The current release is v0.4.3; read its known issues and the limitations before you rely on it. Dokploy and Nomad are experimental for every engine, and several engines are experimental on every provider (engine availability). The main branch, and the documentation on it, can describe changes that are not released yet.

Engines

Versions below are catalog defaults; each engine section lists supported versions and upgrade paths.

Release status and provider-specific availability are centralized in engine availability.

EngineDistribution/versionTopologiesBackupsSection
MongoDBPercona Server for MongoDB 8.0.32-14; Percona Backup for MongoDB (PBM) 2.16.0-1Replica sets; sharded clustersLogical/physical; point-in-time recovery (PITR)MongoDB
RabbitMQRabbitMQ 4.3.61/3/5/7 brokersDefinitions only; no messages or PITRRabbitMQ
ElasticsearchElasticsearch 9.5.5; optional same-version Kibana, Logstash and APM ServerCombined nodes; dedicated mastersNative S3 snapshotsElasticsearch
WeaviateOfficial Weaviate 1.40.1; mixed-license binary, community features onlySingle; 3–9 data members with three fixed Raft votersNative S3 full; no PITRWeaviate
PostgreSQLPercona PostgreSQL 17.11.1 default; majors 16/17/18; extension profilesSingle; Patroni/etcd HA (3/5); Citus distributed; ProxySQL client servicepgBackRest full/diff/incr and PITRPostgreSQL
SupabasePostgreSQL 17 plus release-locked native servicesSame database topologies; modular servicesPostgreSQL data only; separate S3 object protection requiredSupabase
KeycloakOfficial Keycloak 26.8.1; OpenJDK 21One native runtime with a PostgreSQL bindingThrough the source PostgreSQL clusterKeycloak
OpenBaoOpenBao 2.7.11/3/5 members; integrated Raft or bound PostgreSQL storageRaft snapshots to S3; PostgreSQL storage uses source recovery; no PITR for RaftOpenBao
TemporalTemporal 1.32.1 (also 1.31.4); ui-server 2.56.0Combined server; split stateless roles on bound PostgreSQL; Dokploy/Nomad only, not ZeropsSource PostgreSQL backup plus cluster-state manifest; requires binding serviceTemporal
MySQLPercona Server for MySQL 8.4.11-11 default; majors 8.4/8.0Single; Group Replication single-primary (3/5); ProxySQLXtraBackup full/incremental and GTID-based PITRMySQL
Percona XtraDB ClusterPXC 8.4.11-11.1 default; majors 8.4/8.0; separate pxc engine driverGalera cluster (3/5); one ProxySQL-routed writerSeparate PXC backup provenance; full/incremental and PITRPXC
Neo4j CommunityNeo4j 2026.09.0 / 2026.10.0 (default); Temurin Java 21Single member onlyOffline system + graph dumps; full outage; no PITRNeo4j

Providers

Karakoram is multi-platform; a namespace selects the infrastructure provider that provisions its members.

ProviderRole / runtimeInfrastructure and guide
ZeropsReference providerManaged Ubuntu runtimes, Local Storage and public routing in existing projects; guide.
DokployDocker SwarmApplications and node-local volumes on your Dokploy-managed Docker Swarm; guide.
NomadNative jobsNative jobs and dynamic host volumes on your operator-managed Nomad cluster; guide.

See Providers for capability differences and Operating costs for infrastructure costs.

Across engines

  • Catalog-driven creation, resource configuration, disk growth and capability-gated cluster operations.
  • S3-compatible storage, schedules and recovery.
  • Multi-project namespaces and authenticated relays.
  • Monitoring, logs and actor-attributed audit activity.
  • Local accounts, OIDC, namespace-aware RBAC and owner-scoped API tokens: access control.
  • Safe fleet operations, control-plane backup/recovery, notifications and backup drills, verified offline.

Warning: Review critical limits before production use: replica count does not guarantee independent hosts, Local Storage is single-host, and the control plane has one replica.

Quick start

Choose a provider in Providers. For Zerops, use the dashboard-only Quick start, or the installation reference for local deployments, custom names and CLI setup. Dokploy and Nomad installation paths are linked there.

Build from source

Requires Go 1.26+, Node 22.6+, npm and Make:

make build-all             # web UI and both Go executables

make test # Go unit/handler tests

Integration-tagged tests (some require Docker; PostgreSQL/Supabase use native LXC):

go test -tags integration -count=1 -timeout 30m ./...

A Go-only make build without UI assets serves a “UI not built” page. See UI development, Contributing and the end-to-end suite; deployment tests create billable Zerops resources.

Coding agents: read AGENTS.md for repository boundaries and contribution commands.

Documentation index

Keep docs/ beside the repository's api/, ui/ and root README so relative source/reference links resolve.

  • Getting started: Overview · Quick start · Install · Providers · Operating costs · Upgrade
  • Control plane: Architecture · Clusters and operations · Backups and storage · Namespaces and relays · Zerops provider · Dokploy provider · Nomad provider · Monitoring and events · Access control · Security · Operations and troubleshooting · Limitations
  • Interfaces: Web UI · CLI · REST API and SDK · MCP quick start · MCP server · Cluster data MCP
  • Operator agents: karakoram-operator skill · Skill installation
  • Control-plane recovery: State backups and provider rebuild runbooks
  • Backup verification: Scheduled and manual restore drills
  • Notifications: Webhook, Slack and email channels, signatures and delivery guarantees
  • MongoDB: Overview · Replica sets · Sharding · Users, roles and TLS · Backups and PITR · Operations
  • RabbitMQ: Overview · Access and TLS · Definitions backups · Operations
  • Elasticsearch: Overview · Kibana, Logstash and APM · Access and security · Snapshots · Operations
  • Weaviate: Overview · Access and TLS · Backups · Operations
  • PostgreSQL: Overview · Extension profiles: PostGIS, pgvector, TimescaleDB · Service bindings · Distributed Citus · Access and TLS · Backups and PITR · Operations
  • Supabase: Overview · Components and availability · Operations
  • Keycloak: PostgreSQL binding, routing and administrator recovery
  • OpenBao: Overview · API access and TLS · Raft backups and recovery · Operations and unseal
  • Temporal: Overview and prerequisites · Access and TLS · Operations and recovery
  • MySQL and PXC: Overview · Configuration · Access and TLS · Backups and PITR · Operations and recovery · Native verification
  • Neo4j Community: Overview · Access and TLS · Offline backups · Operations
  • Reference: Architecture decisions · Native artifacts · Verification · Contributing · Code of Conduct

Acknowledgements

Thank you to Zerops for providing free-of-charge infrastructure for developing and testing Karakoram. Disclosure: Samyazz, who maintains Karakoram, is employed by Zerops as a system architect. Karakoram is not a Zerops product, and Zerops does not endorse it.

Karakoram installs Percona Server for MongoDB and Percona Backup for MongoDB from Percona's official repositories. It independently implements orchestration; no OpenEverest code or UI is copied into this repository.

License and trademarks

Karakoram uses the [Apache L

Only the beginning is shown; read the rest in the repo

Ask PopNx