Patina vs Reference MCP

Patina and Reference MCP are both agent frameworks tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Patina

Orbit wraps each agent task in a bounded loop: the agent works, validation runs (tests, lint, type checks), and the task only closes when the checks pass. Every loop leaves structured JSON artifacts — what the agent returned, how it scored against a rubric, and a human-readable recommendation to accept, retry, or stop. This makes agent runs auditable after the fact, not just observable in the moment. The ceiling appears when your project needs multi-agent coordination or a hosted execution layer — Orbit is deliberately narrow, self-hosted only, and ships no managed runtime.

Reference MCP

Reference is a local MCP server that reads session transcripts and memory files — CLAUDE.md, AGENTS.md, and similar — from multiple AI coding tools, then exposes that history to whichever agent is asking. Register it once in each tool's MCP config and any agent can query what any other agent did before. The architecture is passive: Reference does not plan, execute, or chain tasks — it answers lookups. That scope is the point, and also the ceiling. Teams with more than a handful of tools, or who need structured, queryable memory rather than transcript search, will find the file-scanning approach starts to feel fragile as session volume grows.

Attribute	Patina	Reference MCP
Pricing	Free	Free
Free trial	No	No
Open source	Yes	Yes
Has API	No	No
Self-hosted option	Yes	Yes
Platforms	Python (via pip install), local execution, CLI	Python / local
Pros	Validation gates block task closure until tests, lint, and type checks pass, so agents cannot self-report success on work that would fail your CI pipeline. Four structured artifacts per run (agent output, rubric evaluation, review recommendation, and progress log), which means audit trails exist by default instead of requiring you to reconstruct what happened from logs. Dependency-ordered backlog selection keeps each loop focused on one task at a time, so agents do not skip prerequisites or work on tasks whose dependencies are not yet verified. Agent-neutral adapter contract lets you swap Claude, Codex, Cursor, or any JSON-speaking CLI behind the same harness, so you compare agents on identical tasks with structured artifacts instead of anecdotes. MIT licensed and fully self-hosted, so teams with on-premise requirements or external platform restrictions can run the full harness without a managed dependency.	Reads session transcripts from Claude Code, Codex CLI, and Cursor in one place, so you stop re-explaining decisions that were already made in a different tool last week. Fully local and offline, which means code and conversation history never leave your machine — critical for projects where sending context to a third-party sync service is off the table. MIT-licensed with no paid tiers and no account required, so there is no vendor relationship to manage and no access cliff if a pricing tier changes. Single MCP registration pattern works across supported tools, so you configure it once per tool rather than wiring a custom integration for each pair.
Cons	Orbit handles one task per loop; there is no mechanism for running agents in parallel or coordinating handoffs between agents. Teams whose workflows require concurrent agent execution build a separate scheduling layer on top — at which point they are maintaining two systems. The harness ships no hosted runtime, no API, and no managed execution environment. Teams that want cloud-hosted agent scheduling or need to trigger runs from external CI systems without standing up their own infrastructure will move to a platform that provides those primitives. The adapter and demo ecosystem is early-stage and contribution-dependent. Teams integrating a coding agent that lacks an existing adapter write and maintain the adapter themselves, which adds setup cost before the first validated loop runs.	Search runs over raw transcript files and markdown — not a structured index. Once session volume is high enough that the answer you need is buried in dozens of transcripts, recall becomes a best-effort grep rather than a reliable query, and teams at that point look at purpose-built vector stores like a local Chroma or Weaviate instance instead. Memory is local to one machine. A team of two engineers running the same agents on different laptops gets zero shared context — Reference has no sync layer. Teams who need shared agent memory across contributors abandon this and wire a shared database backend, at which point Reference's architecture no longer fits. There is no API and no programmatic query surface outside the MCP protocol. Any workflow that needs to pull agent history into a dashboard, a CI pipeline, or a custom tool has no supported path — the docs describe no extension point for that use case.

Bottom line

Patina and Reference MCP are closely matched on pricing model, openness, and API availability — pick by feature set and platform support in the table above.

Frequently asked questions

What is the difference between Patina and Reference MCP?

Patina is Free and open source, while Reference MCP is Free and open source. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Patina better than Reference MCP?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.