Preseason.ai vs Reference MCP

Preseason.ai 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.

Preseason.ai

Orbit sits between your backlog and your coding agent, selecting one dependency-ordered task at a time, running the agent, then forcing the result through tests, lint, and type checks before marking the task done. Every run writes structured JSON artifacts — what the agent returned, how the output scored against a rubric, whether a human should accept or iterate — so you are reviewing evidence, not trusting a diff. The agent-neutral contract means you can run Claude, Codex, and Cursor against the same task and compare artifacts instead of impressions. The harness is intentionally minimal; it does not schedule, it does not host, and it does not manage secrets — which means the moment your workflow needs cross-repo coordination or cloud execution, you are writing the glue yourself.

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	Preseason.ai	Reference MCP
Pricing	Free	Free
Free trial	No	No
Open source	Yes	Yes
Has API	No	No
Self-hosted option	Yes	Yes
Platforms	Linux, macOS, Windows (CLI/Python-based)	Python / local
Pros	Validation gates enforce proof before task completion, so a coding agent cannot mark a fix done while tests are still failing — which eliminates the silent regression problem that plagues unguarded agent loops. Agent-neutral adapter contract means you can run Claude, Codex, and Cursor against identical tasks and compare structured evaluation artifacts, so you stop arguing about which agent is better and start looking at data. Four machine-readable artifacts per orbit (agent result, evaluation, recommendation, progress log) give audit teams a complete, inspectable record of what the agent returned and how validation scored it — without relying on anyone's memory of what happened. Dependency-ordered backlog selection keeps each agent run focused on one unblocked task, which means agents cannot start work that depends on incomplete prior steps — a failure mode that costs hours of untangling in unconstrained agent loops. Deterministic replay with no API key required means you can verify the harness behavior itself in isolation, so debugging a broken validation run does not require burning API credits or standing up a live agent.	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 has no scheduler, no cloud execution layer, and no cross-repo awareness — the moment your workflow requires tasks that span more than one repository or need to run on remote infrastructure, you are assembling that plumbing yourself on top of the harness. The adapter contract requires agents to speak JSON over CLI, so agents with browser-only or proprietary API interfaces need a wrapper built before they can run inside an orbit — that wrapper is not provided and is the team's responsibility to maintain. Orbit has no built-in backlog management UI or integration with issue trackers; the backlog is whatever structured input you feed it, which means teams used to Jira or Linear-driven workflows will spend setup time before the first orbit runs. Teams that need parallel agent execution — running multiple tasks simultaneously to cut wall-clock time on large backlogs — will hit the single-orbit-at-a-time model as a hard ceiling and switch to a purpose-built agent orchestration platform rather than extending Orbit.	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

Preseason.ai 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 Preseason.ai and Reference MCP?

Preseason.ai 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 Preseason.ai 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.