Karakoram

Name: Karakoram
Author: KarakoramDev

作者：KarakoramDev版本 0.4.3i★ –i在云端运行

注册名称io.github.KarakoramDev/karakoram

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 数据库与数据集
你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

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

运行前请先填写空着的值。

地址中有只有你知道的 {…} 部分（例如你的账户），请复制后自行填写。

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

地址中有只有你知道的 {…} 部分（例如你的账户），请复制后自行填写。

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

Authorization 机密必填 HTTP header
Karakoram API token; `karactl mcp config` mints a restricted, read-only one

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

这个地址需要填入你自己的值，所以我们无法替你读取工具列表。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 KarakoramDev 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
这个地址需要填入你自己的账户信息，所以我们无法替你检查
– 不适用
使用 OAuth 登录
这个地址需要填入你自己的账户信息，所以我们无法替你检查
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“数据库与数据集”中的其他服务器比较i

星标数多于此分类中其他 955 个服务器的 0%
发布到注册中心的时间比此分类中其他 955 个服务器的 93% 更新
基础检查结果等于或优于此分类中其他 955 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Karakoram 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：Authorization

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.4.3）于3天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Supabase, MongoDB MCP Server, Elasticsearch MCP Server

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Supabase

作者：supabase

MCP server for interacting with the Supabase platform

电脑或云端★ 2,993Apache-2.0昨天更新

安装

MongoDB MCP Server

作者：mongodb-js

MongoDB Model Context Protocol Server

在你的电脑上运行★ 1,157Apache-2.03天前更新

安装

Elasticsearch MCP Server

作者：cr7258

MCP server for interacting with Elasticsearch

在你的电脑上运行★ 315Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.

Engine	Distribution/version	Topologies	Backups	Section
MongoDB	Percona Server for MongoDB 8.0.32-14; Percona Backup for MongoDB (PBM) 2.16.0-1	Replica sets; sharded clusters	Logical/physical; point-in-time recovery (PITR)	MongoDB
RabbitMQ	RabbitMQ 4.3.6	1/3/5/7 brokers	Definitions only; no messages or PITR	RabbitMQ
Elasticsearch	Elasticsearch 9.5.5; optional same-version Kibana, Logstash and APM Server	Combined nodes; dedicated masters	Native S3 snapshots	Elasticsearch
Weaviate	Official Weaviate 1.40.1; mixed-license binary, community features only	Single; 3–9 data members with three fixed Raft voters	Native S3 full; no PITR	Weaviate
PostgreSQL	Percona PostgreSQL 17.11.1 default; majors 16/17/18; extension profiles	Single; Patroni/etcd HA (3/5); Citus distributed; ProxySQL client service	pgBackRest full/diff/incr and PITR	PostgreSQL
Supabase	PostgreSQL 17 plus release-locked native services	Same database topologies; modular services	PostgreSQL data only; separate S3 object protection required	Supabase
Keycloak	Official Keycloak 26.8.1; OpenJDK 21	One native runtime with a PostgreSQL binding	Through the source PostgreSQL cluster	Keycloak
OpenBao	OpenBao 2.7.1	1/3/5 members; integrated Raft or bound PostgreSQL storage	Raft snapshots to S3; PostgreSQL storage uses source recovery; no PITR for Raft	OpenBao
Temporal	Temporal 1.32.1 (also 1.31.4); ui-server 2.56.0	Combined server; split stateless roles on bound PostgreSQL; Dokploy/Nomad only, not Zerops	Source PostgreSQL backup plus cluster-state manifest; requires binding service	Temporal
MySQL	Percona Server for MySQL 8.4.11-11 default; majors 8.4/8.0	Single; Group Replication single-primary (3/5); ProxySQL	XtraBackup full/incremental and GTID-based PITR	MySQL
Percona XtraDB Cluster	PXC 8.4.11-11.1 default; majors 8.4/8.0; separate `pxc` engine driver	Galera cluster (3/5); one ProxySQL-routed writer	Separate PXC backup provenance; full/incremental and PITR	PXC
Neo4j Community	Neo4j 2026.09.0 / 2026.10.0 (default); Temurin Java 21	Single member only	Offline system + graph dumps; full outage; no PITR	Neo4j

Providers

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

Provider	Role / runtime	Infrastructure and guide
Zerops	Reference provider	Managed Ubuntu runtimes, Local Storage and public routing in existing projects; guide.
Dokploy	Docker Swarm	Applications and node-local volumes on your Dokploy-managed Docker Swarm; guide.
Nomad	Native jobs	Native 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

只显示了开头部分；其余内容请在仓库中阅读

Karakoram

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“数据库与数据集”中的其他服务器比较i

常见问题

替代选择

Supabase

MongoDB MCP Server

Elasticsearch MCP Server

作者的 README

Karakoram

Engines

Providers

Across engines

Quick start

Build from source

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

Documentation index

Acknowledgements

License and trademarks