MCP
Understand how the Mecharim MCP surface helps agents discover the platform, read machine contracts, and bootstrap integration.
Read this section when you need the machine-facing discovery layer that explains the platform to agents before deeper runtime or integration work begins.
Before you continue
Read these first if you want the current page to make more sense in the wider handbook.
MCP is the machine-facing discovery and contract layer. It helps an agent understand the Mecharim ecosystem, find stable shapes, and bootstrap itself without confusing discovery with live transport or business runtime.
What this section should answer
- What the MCP surface is actually for
- What an agent should discover before it tries to act
- How MCP differs from Mecha runtime transport
- How schemas, descriptors, and examples should be structured
- Where machine discovery stops and live operational access begins
Responsibilities
| Responsibility | Description |
|---|---|
| Platform description | Explains the Mecharim ecosystem in machine-usable terms |
| Discovery bootstrapping | Gives agents a stable place to orient before runtime work |
| Worked examples | Gives concrete request and response patterns for tooling and implementation |
| Schema access | Exposes machine-readable structures for validation and tooling |
Where to go next
- Continue with MCP Overview if you want the cleanest conceptual starting point.
- Continue with Discovery if you are designing the first machine-facing handshake.
- Continue with Examples if you want concrete flow patterns.
Design rule
The MCP surface should stay flat, explicit, and highly parseable. It is a contract for machines first, not a marketing page.
Related pages
Open these pages when you want adjacent concepts, neighboring entities, or connected implementation context.
MechaReg
MechaReg is the public trust and discovery surface of the platform, the layer that projects grounded business reality into machine-readable visibility.
Mecharim Documentation
Documentation for the Mecharim platform.
Connect a Mecha Runtime
This is the first live runtime step, the point where the configured Mecha becomes an operating actor connected over real transport.
Next reading
Use this path if you want a cleaner progression through the handbook after this page.
MCP Overview
Start here if you want the cleanest explanation of what the MCP layer is for, what it should expose, and what it should not try to do.
Discovery
This page explains the first machine-facing handshake, what an agent needs to learn before deeper integration and why discovery should stay boring.