Developers
StableDeveloper
API vs MCP
Choose the right Blocchi headless interface without creating two business contracts.
REST and MCP expose the same governed capability layer but optimize for different clients.
| Use | Prefer |
|---|---|
| Durable software integration | REST API |
| ETL, backend service or scheduled integration | REST API |
| AI agent discovering what Blocchi can do | MCP |
| Conversational orchestration with structured tool discovery | MCP |
| Stable machine contract for generated clients | REST/OpenAPI |
| Agent learning the REST contract before choosing an endpoint | MCP blocchi.describe_api |
Rule of thumb
REST is the durable integration contract. MCP is the agent-facing adaptation and discovery layer.
Do not add business logic only to an MCP handler. A capability should exist as a governed application service first, then be exposed through the appropriate REST/MCP surfaces.
Last updated on