1# mcp-contract.manifest.yaml
2# a project-structure spec for claude extensions
3# that have outgrown a single file
4
5version: "0.1.0-draft"  # in active revision; not pinned
6status:  "shipped"        # spec is real, adopters are not (yet)
7price:   "free"           # MIT
8
9# claude is a compiler. everything else is portable.
10# prompts compile to outputs the way C compiles to a binary —
11# the source travels, the compiler stays where it is.
12
13layers:

19
20# graph: providers and consumers, resolved by the compiler.
21
22graph:
23  - capability:    doc.contract_pdf
24    provided_by:   tools.contract_parser
25    consumed_by:   prompts.draft_review
26    state:         satisfied             ✓
27
28  - capability:    analysis.risk_report
29    provided_by:   prompts.draft_review
30    consumed_by:   apps.summary_panel
31    state:         satisfied             ✓
32
33  - capability:    fn.execute_script
34    provided_by:   tools.script_runner
35    consumed_by:   skills.claude_dispatch
36    state:         satisfied             ✓
37
38  - capability:    ui.export_handler
39    provided_by:   ~                          # no provider
40    consumed_by:   apps.export_handler
41    state:         unsatisfied           ✗
42
43# 1 unsatisfied. mcpc validate, below, names it.

44
45# the contract. every component declares what it provides;
46# every component declares what it consumes. the compiler
47# checks that the graph is satisfied.
48
49example_manifest:
50  provides: ["analysis.risk_report"]
51  consumes: ["doc.contract_pdf"]
52
53# run this against your repo. it will tell you exactly
54# which capabilities are unsatisfied and which are orphaned.
55
56cli:

$ pip install mcpc-cli
Successfully installed mcpc-cli-0.1.0-draft

$ mcpc validate
  reading  ./mcp-contract.manifest.yaml
  found    4 layers · 7 components · 12 arcs

  ✓ prompts.draft_review     provides analysis.risk_report
  ✓ tools.contract_parser     provides doc.contract_pdf
  ✓ apps.summary_panel      consumes analysis.risk_report
  ! apps.export_handler     consumes ui.export_handler — unsatisfied

  result   1 unsatisfied capability — see graph above
  exit     1

$ █

57
58# reference implementation. the first claude extension
59# built against this contract. it works; it's also still
60# in active build. honest framing on its own page.
61
62reference_implementation:
63  slug:  "synth-ops"
64  role:  "first deployed extension built against this contract"
65  href:  "/sku/synth-ops"
66
67# source. the repo is the artifact. the readme tells the
68# story better than this page can.
69
70source:
71  github: "jmfullerton96/mcp-contract"
72  readme: "README.md"
73
74# notes from the author.
75
76notes: |

77 The repo is public. The readme tells the story better than I can. I might've invented the problem — that's fine. Accuracy over prizes.

78 What this is: a project template for MCP extensions past the single-file stage. Layers, manifest, contracts, a reference impl.

79 What this isn't: a framework anyone needs to adopt. docker-compose for MCP it is not. Use the parts that help you.

80 — joe@jibeworks.com

81
82# EOF