Developers · over MCP

Plug Maven into anything.No per-vendor wiring.

Maven is an MCP server. Claude, Cursor, your Slack bot, and your custom agents all read and write the same governed truth through one endpoint. Switch models tomorrow and nothing else changes.

Abstract line-art of one shared memory feeding many assistants over MCP

§01

For developers

Three tools. Any assistant. Over MCP.

get_current_truth(entity, key)

The authoritative value right now, with its source, approver, and validity window.

get_history(entity, key)

Every version over time: what changed, when, and which fact superseded which.

record_decision(payload)

Write a new decision back, with provenance and fact-level permissions attached.

Point your MCP client at Maven. No per-vendor integration, no SDK lock-in.

§02

Proof, not promises

One MCP call, fully governed.

// any assistant, over MCP
maven.get_current_truth({
  entity: "service/billing",
  key: "api.timeout",
  as_of: "now"
})

// → resolved, with provenance
{
  value: "60s",
  valid_from: "2026-06-12",
  valid_to: null,  // current
  source: "ADR-114",
  approved_by: "@cto",
  supersedes: "fact#8420",
  audit: "evt_8821"
}

Every read comes back resolved: the current value, when it became true, who approved it, what it superseded, and an audit id. The same call from any assistant, with the same governed answer.

§03

Get started

Make every decision provable.

Start with one engineering team and the decision-memory wedge, then grow across the org on the same governed spine. No migration project, no rip-and-replace, no begging people to change tools.

See how it plugs in

Plugs in over MCP · keep every tool you already use · one brain behind them