Skip to main content
Platform features are currently in invite-only beta. You can sign up here if you want to be considered for one of our next phases. The open source CLI, the compiler and the standalone generator are not part of the beta and are available now.
Not built yet. There is no Cordango MCP server to connect to. This page records the intended design so the shape is not invented twice. Nothing here is a stable contract, and no tool names on this page should be relied on.

​
The intent

An app is meant to have three faces over one security, entitlement and audit layer:

UI

The rendered application people use.

REST

Baseline on every app. See the API reference.

MCP

The same operations, addressed by an AI client.
The point of the split is that MCP is not a separate integration with its own permission model. It projects the operations that already exist, through the same checks the REST facade goes through, so an AI client acting as you can reach exactly what you can reach.

​
What exists today

The REST facade is real and documented. It is generated from the app’s manifest, and each app publishes its own OpenAPI document:
Until there is an MCP server, that document is the practical route for an AI client: point a tool generator at it and you get the app’s real entities and fields rather than a generic shape.

​
Open questions

These are undecided rather than merely undocumented:
  • Transport specifics, streamable HTTP and resumability.
  • Whether a per-app server, a workspace-level aggregator gateway, or both.
  • Tier gating. MCP is planned as a paid-tier feature.
When the server lands, this section gets a real tool reference. Until then, treat anything claiming to document Cordango MCP tools as fiction.