Publish MCP server changes with confidence.

0mcp separates the latest server configuration from the revision serving live traffic. Review tools, resources, and prompts in an immutable revision, compare it with the live version, then publish or roll back deliberately.

Start free trialRead docs
server-revisions
Draft ready

Candidate revision

Review before publishing

01Compare capabilities with live
02Review tools, resources, and prompts
03Publish or restore a revision

Release control

Draft compared with live

Revision

IMMUTABLE

Diff

REVIEWABLE

Rollback

AVAILABLE

Keep MCP changes visible and reversible

Immutable revision history

Preserve each generated server revision with its capability counts and creation context.

Live-versus-draft comparison

See what changed between a candidate revision and the version currently serving traffic.

Deliberate publishing

Keep configuration work separate from the published revision until reviewers are ready.

Rollback support

Republish a previous revision when a newer capability set should not remain live.

Change control

Separate editing from live traffic

Own every infrastructure detail, or start from your OpenAPI contract with a managed platform.

Unversioned changes

  • Configuration changes become difficult to trace
  • Review happens after clients see changes
  • Recovery requires recreating old settings

0mcp revisions

  • Every capability set has a revision
  • Compare a candidate with the live version
  • Republish a previous immutable revision

When MCP versioning matters

01

API specification updates

  • Review added or removed operations
  • Confirm changed input schemas
  • Publish on your schedule

02

Tool description changes

  • Refine agent-facing guidance
  • Compare before release
  • Retain the prior behavior

03

Production recovery

  • Identify the live revision
  • Return to a known capability set
  • Investigate without rebuilding it

FAQs

What is an MCP server revision?

A revision is an immutable snapshot of the tools, resources, prompts, and related configuration generated for an MCP server at a point in time. One revision can be published while a newer revision remains available for review.

Do configuration changes immediately affect the live server?

No. 0mcp tracks the latest revision separately from the published revision. A candidate capability set does not become the live version until it is explicitly published.

Can I compare a revision with the live version?

Yes. The revision workflow compares a selected revision with the published version so reviewers can see capability additions, removals, and changes before deciding to publish.

Can I roll back an MCP server?

Yes. Because earlier revisions are immutable, an eligible previous revision can be published again to restore that known capability set.

Ship MCP changes without losing the last known version.

Create immutable revisions, compare them with live, and publish or roll back from one workflow.

Start free trial