Add server: bernstein

[chernistry]

Adds a registry manifest for bernstein, an MCP server that exposes a deterministic orchestrator for CLI coding agents.

What it does. Bernstein runs Claude Code, Codex, Gemini CLI, Aider and 40+ other agent CLIs in parallel inside isolated git worktrees. Every run is recorded in a replay journal with lineage tracking, plus an optional HMAC-chained audit log that can be verified offline.

MCP surface. The manifest documents the 13 tools advertised at the default tool tier (bernstein_health, bernstein_run, bernstein_status, bernstein_tasks, bernstein_cost, bernstein_claim, bernstein_update, bernstein_post_artifact, bernstein_stop, bernstein_approve, bernstein_create_subtask, bernstein_task_handle, load_skill), 2 resources, and 3 prompts. Five further tools (scenario bridge and lineage chain verification) are available when the server is started with --mcp-tier all.

Tool names, descriptions and input schemas in this manifest were taken from a live tools/list against the published 3.9.0 package, not written by hand.

Details

• Package: bernstein on PyPI, 3.9.0
• Source: https://github.com/sipyourdrink-ltd/bernstein
• License: Apache-2.0
• Requires Python 3.12+
• Local only, stdio transport, no API key required

Checks

• python scripts/validate_manifest.py | grep bernstein gives ✓ bernstein: Valid
• Both documented install methods were run against 3.9.0 and answer initialize and tools/list over stdio.

Submitted by the project maintainer.

Summary by CodeRabbit

• New Features
  • Added the official “bernstein” MCP server to the registry.
  • Provides deterministic multi-agent orchestration with run lifecycle, task claiming, progress journaling, approvals, subtasks, artifact posting, cost reporting, and graceful shutdown.
  • Includes context access for tasks, skill loading for extending capabilities, and built-in orchestration prompts for goal handling, failed-task triage, and cost recap.
  • Adds server metadata plus installation and usage guidance, including capability and lineage JSON resources.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3c61237e-c2e8-479f-b79e-e74c9b1e56e4

📥 Commits

Reviewing files that changed from the base of the PR and between 3b9302d and e964822.

📒 Files selected for processing (1)

• mcp-registry/servers/bernstein.json

🚧 Files skipped from review as they are similar to previous changes (1)

• mcp-registry/servers/bernstein.json

---

📝 Walkthrough

Walkthrough

Adds the Bernstein MCP server to the registry with installation metadata, orchestration tools, skill loading, built-in prompts, capability and lineage resources, usage examples, and official-server status.

Changes

Bernstein MCP registry integration

Layer / File(s)	Summary
Server metadata and installation mcp-registry/servers/bernstein.json	Defines the server identity, repository and licensing metadata, categories, tags, installation methods, and example prompts.
Orchestration tool contracts mcp-registry/servers/bernstein.json	Declares health, run lifecycle, cost, task claiming, signed updates, artifact posting, shutdown, approvals, subtasks, task handles, and context retrieval.
Skills, prompts, and resources mcp-registry/servers/bernstein.json	Adds the load_skill tool, three built-in prompts, capability and lineage resources, and the is_official marker.

Estimated code review effort: 3 (Moderate) | ~30 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately summarizes the main change: adding the Bernstein MCP server manifest.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[qodo-code-review]

PR Summary by Qodo

Add Bernstein MCP server manifest to registry

✨ Enhancement ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Add Bernstein as an official MCP server entry in the registry.
• Document install/run commands (uvx and existing Python install) for local stdio use.
• Publish tool schemas plus prompts/resources for orchestrating and auditing agent runs.

Diagram

graph TD
  repo["MCP registry"] --> manifest["mcp-registry/servers/bernstein.json"] --> client(["MCP client"]) --> pkg["PyPI package: bernstein 3.9.0"] --> server["Bernstein MCP server (stdio)"]
  server --> client

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. CI-driven manifest regeneration from `tools/list`

• ➕ Reduces drift between published package behavior and registry schemas
• ➕ Makes version bumps easier by re-snapshotting the MCP surface
• ➖ Requires executing the server/package in CI (environment/tooling complexity)
• ➖ Introduces risk of transient failures or platform-specific differences affecting registry updates

2. Version-pinned manifests per upstream release

• ➕ Allows clients to target a known server schema/version combination
• ➕ Makes breaking MCP surface changes explicit in the registry history
• ➖ Increases registry maintenance burden and noise (multiple manifests per server)
• ➖ Requires additional client-side logic to choose versions

Recommendation: Keep the current static manifest approach (fits the registry model and is easy to validate). If schema drift becomes an issue, consider adding an opt-in CI job that periodically re-snapshots tools/list for maintainers, without making it a hard PR requirement.

Files changed (1) +589 / -0

Other (1) +589 / -0

bernstein.jsonAdd official Bernstein server registry manifest +589/-0

Add official Bernstein server registry manifest

• Introduces a new MCP registry entry for the Bernstein orchestrator, including repository/author/license metadata and installation methods (uvx and existing Python install). Documents the MCP surface area by listing tools with input schemas, plus built-in prompts, resources, and usage examples; marks the entry as official.

mcp-registry/servers/bernstein.json

[Copilot]

Pull request overview

Adds a new MCP registry manifest for the bernstein server so it can be discovered and installed via the registry.

Changes:

• Introduces bernstein server metadata (repo/homepage/author/license, categories/tags).
• Documents installation methods (uvx recommended, plus an existing Python install entrypoint).
• Captures the server’s advertised MCP surface (tools, prompts, resources) in the registry format.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review