Reference resolver for the ribosome standard: mise + MCP registry adapters, phased materialization into one reproducible lockfile.
Upfront dependency materializer for tool/runtime versions and MCP servers.
Given a project's declared runtimes and MCP servers, ribosome resolves and materializes them before any workflow runs — deduplicating runtimes into a shared pool and pinning everything into one reproducible lockfile — so missing tools or unresolvable servers fail at validation time, not mid-execution.
The ecosystem already has runtime managers (mise, asdf, nix) and MCP clients that read server.json and launch servers. Nobody unifies the two: resolve your runtimes and your MCP servers together, dedup shared runtimes, and pin a single reproducible lockfile — up front.
ribosome fills exactly that gap. It conforms on the config axis (its mcpServers section is a compatible superset of existing MCP config formats) and competes on the runtime axis (the provisioning those formats don't do).
- ribosome-schema — the standard: normative JSON Schemas for ribosome.json/ribosome.lock.json, a conformance corpus, and a TypeScript binding. Apache-2.0. - ribosome (this repo) — the reference resolver/orchestrator: pluggable runtime + MCP registry provisioning, and the materialization pipeline. MPL-2.0 — see Licensing.
ribosome depends on @medullaflow/ribosome-schema as an ordinary package, the same way it depends on any other library. This repo carries no schema, no JSON Schema files, no conformance fixtures — see ribosome-schema for those.
From the project README.
Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:
[](https://mcp.liqiwa.com/s/medullaflow--ribosome.html)
MCP server for Claude Desktop and other Model Context Protocol clients — sandboxed filesystem access (read/write/edit/search) plus Dev Mode-gated shell command execution, scoped to a single workspace
sanjayrohith/DejavuRepository-scoped memory for coding agent's decisions, pitfalls, and handoffs stored in one inspectable SQLite file, so agents continue instead of starting over.
Blackman99/real-botAlpha: local-first macOS app for persistent AI teammates, open model endpoints, and MCP tools
appautomaton/pi-arcweldAn auditable local workspace for Pi: pinned upstream source, curated extensions, bounded MCP tooling, and a reproducible external runtime.
yiaany/MekkaThe agent-native Supabase killer: SQLite speed today, distributed cloud next, without the PostgreSQL tax.
IrMaho/TeleDOM⚡ Temporal Browser Intelligence & Agent-Owned Workflow Runtime with 350 Certified MCP Tools & Python SDK · Sub-Millisecond DOM Time-Travel, Target Memory & Deterministic Automation.
The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.