Connect agents to your app.
Turn on MCP to let Claude and other agents use your app safely. They can work with your app's data and workflows, while each user keeps the right access. The REST API is included too.
Billing Ops entities and workflows map into generated MCP tools for agents.
How it works
Your app's own MCP server.
Turn on MCP, and your app has a POST /mcp endpoint. Each on-demand workflow becomes a tool. Each entity gets list, read, create, and update actions, with access scoped to the signed-in user.
REST plus OpenAPI, the interface agents read
Your data model creates a REST API and an OpenAPI 3.0 schema at /openapi.json.
An llms.txt so answer engines find your app
Every app publishes an llms.txt file so LLMs and answer engines can understand your app.
An MCP server built from your app.
Your workflows and entities become MCP tools with token auth and signed-in user scope.
REST plus OpenAPI, the interface agents read
Your data model creates a REST API and an OpenAPI 3.0 schema at /openapi.json. Agents can read the spec to understand your app and call the right API routes.
REST plus OpenAPI, the interface agents read
Your data model creates a REST API and an OpenAPI 3.0 schema at /openapi.json.
An llms.txt so answer engines find your app
Every app publishes an llms.txt file. It lists your app's pages in plain text, so LLMs and answer engines can understand your app and direct people to it.
Where it stops: llms.txt today describes your app's pages, not its API endpoints.
An llms.txt so answer engines find your app
Every app publishes an llms.txt file so LLMs and answer engines can understand your app.
An MCP server built from your app.
Your workflows and entities become MCP tools. They use the same rules as your REST API, so access and validation stay consistent. Agents connect with a personal access token that you can revoke anytime.
Where it stops: MCP is opt-in per app, and agents without a token see only your public workflow tools.
An MCP server built from your app.
Your workflows and entities become MCP tools with token auth and signed-in user scope.
Where it fits
Build the app once. Every caller reads the same shape.
Everything uses the same data model: your screens, REST clients and agents. Draw the model once and all three read it.
Ship an app agents can drive
Build your app, turn on MCP, and agents connect to your workflows and data with a token.
Créé avec Orbit