Consensus

io.github.masterblaster14由 GitHub 账号 masterblaster14 发布v0.1.0更新于 Oct 27, 2026

Coordination for AI coding agents: declare plans, catch design conflicts early, share team memory.

已验证Streamable HTTP可网页运行效率与工作流知识与记忆开发者工具

概览

AI 生成的概览

面向 AI 编码代理团队的协调服务器：代理在写代码前申报计划，获得继续或等待的裁决，并共享团队记忆。

可以做什么
  • 申报编码计划，并对照其他进行中的计划和既往裁决获得裁决（继续、带上下文继续或等待）
  • 查询裁决结果，并在计划变更或放弃时撤回申报
  • 查询团队共享记忆，记录发现、决策和走过的死路
  • 提交交接说明，写明改了什么、没动什么、假设了什么
  • 查看状态并上报所连接开发者密钥的使用情况
适用场景
适合多名开发者各自在同一代码库上运行 AI 编码代理的团队，希望在代码出现之前就发现设计冲突，并通过共享记忆避免重复阅读代码和重复踩坑。也适合希望把人工裁决自动套用到后续冲突计划的团队。
运行要求
远程 MCP 端点，使用 streamable HTTP；需要 Consensus 设置页生成的个人 API 密钥，以 Authorization Bearer 头发送。需要 Consensus 账号（GitHub 或邮箱登录）和组织，GitHub、Notion 集成为可选。自托管需要 Python 3.11、带 pgvector 的 PostgreSQL 和 Redis。
安装前请注意
该 API 密钥是个人凭证，所有操作都会归属到密钥所属开发者，不要放进共享配置。计划、记忆条目和交接内容会发送到托管服务并对团队可见。交接可创建拉取请求、裁决可作为 PR 评论发布，因此会写入 GitHub。托管实例涉及收费。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Consensus，将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.masterblaster14%2Fconsensus/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "consensus": {
      "type": "http",
      "url": "https://consensus-production-aed6.up.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Consensus

Coordination for teams whose developers each run an AI coding agent on the same codebase.

Before an agent writes code, it declares its plan. Consensus checks that plan against every other plan in flight and against what the team already knows, and answers in a second: proceed, proceed with context, or wait.

Why

AI coding agents are fast and they work alone. On a team that produces two problems git cannot see:

  • Design conflicts in files that never touch. One agent moves sessions to signed tokens; another adds a login endpoint that assumes server-side sessions. No merge conflict. Two incompatible designs discovered days later in review.
  • Every agent starts from zero. The same code gets re-read, the same dead ends get re-tried, and nothing one agent learns reaches the next.

What it does

  • Declare before writing. Plans are compared on what they mean, not which files they touch. Conflicts are caught before the code exists.
  • Shared memory. Agents ask what the team knows before reading the codebase, and record discoveries, decisions and dead ends as they work.
  • Human rulings that compound. When two plans genuinely conflict, a person decides once. The ruling is stored and applied automatically to every future plan that would raise the same conflict.
  • Clean handoffs. When work is done, the agent files what changed, what it left alone, and what it assumed. That becomes the pull request.

Consensus never reads, writes, executes or merges code.

How it works

  1. One language-model call extracts a plan's stance: the concepts it touches and its positions on error handling, authentication, data access and API shape. Unaddressed axes stay empty; nothing is guessed.
  2. The nearest open plans and memory entries are retrieved by vector search.
  3. Plans are compared deterministically. Shared concept plus disagreeing positions is a clash. Same inputs, same answer, every input logged.
  4. A hard clash is checked against prior rulings before any human is asked.

Full detail: How it works.

Connecting an agent

Consensus is an MCP server. Each developer creates a personal API key (settings page, or POST /api/me/api-keys) and connects their coding agent to it.

Claude Code, with the guardrail (recommended). The plugin adds the server, a skill that teaches the workflow, and a hook that refuses Edit/Write until the plan is declared and the verdict allows it:

bash
export CONSENSUS_API_KEY="csk_..."          # CONSENSUS_URL defaults to the hosted instanceclaude plugin marketplace add masterblaster14/Consensusclaude plugin install consensus@consensus

Claude Code, server only:

bash
claude mcp add --transport http consensus https://consensus-production-aed6.up.railway.app/mcp --header "Authorization: Bearer csk_..."

Cursor, Windsurf, any MCP client. Add to the client's MCP config:

json
{ "mcpServers": { "consensus": { "url": "https://consensus-production-aed6.up.railway.app/mcp", "headers": { "Authorization": "Bearer csk_..." } } } }

Listed in the MCP Registry as io.github.masterblaster14/consensus, so registry-aware clients can find it by name.

Everything an agent does is attributed to the developer who owns the key. The tools: declare_intent, check_verdict, query_memory, write_memory, file_handoff, withdraw_claim, get_status, report_usage.

Teams and integrations

  • Sign in with GitHub or an email link. The first person to create an organisation is its admin; others join by invite link or by email domain.
  • One shared live board per repository.
  • GitHub: handoffs open pull requests, rulings become PR comments, merged PRs retire their plans.
  • Notion: tasks sync in, decisions and rulings mirror out.

Hosted instance: https://consensus-production-aed6.up.railway.app (API docs at /docs, live board at /board).

Running it

Python 3.11, PostgreSQL with pgvector, Redis. Docker Compose for the databases. Offline mode needs no API keys.

docker compose up -d.venv/Scripts/python -m alembic upgrade head.venv/Scripts/python -m scripts.seed_demo.venv/Scripts/python -m uvicorn app.main:app --port 8000

Or the whole stack in containers: docker compose --profile full up -d --build.

Setup details, configuration and the full API: Backend reference. Hosting it: Deploying (Render blueprint, Railway, Fly, or any Docker host).

License

MIT. See LICENSE.

Documentation

来源：README.md，提交 94d9bcd

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

1
  1. v0.1.0最新Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分