Who can use what
Each part of your app says who may use it, such as anyone signed in or only people with a certain permission. This is settled before any of your code runs.
Jets
Built into every app
Jets
Built into every app
How it works
There is no MCP server to write and no sign-in code to add. Every functionality of your app becomes a tool, and each agent signs in as the person it works for.
Every functionality of your app becomes a tool an agent can use, from the first deploy. You choose which tools to offer, and you can name and describe each one.
They add your-app.substrio.com/mcp in Claude, ChatGPT, Claude Code, or Cursor, and sign in on your app's consent page. A script can use an agent token instead.
Everything the agent does runs as that person, under the same rules as your app. The agent can do what the person can do, and nothing more.
Safe by design
An agent never gets more access than the person it works for. It passes the same checks as that person does on your site.
Each part of your app says who may use it, such as anyone signed in or only people with a certain permission. This is settled before any of your code runs.
The rules on your data, and the person's role and permissions, apply to everything the agent reads and changes.
Each call uses the permissions the person holds at that moment. A role you lower or an account you disable takes effect on the next call.
A user can disconnect any agent in one step. When you disable a user, every agent of that person stops on its next call.
A user's agent gets your app's tools and nothing else. The tools for running your app are only available with your app key.
Every time an agent uses a tool, it is counted. A record is kept of every agent connection, who made it, and when it was revoked.
Why it matters
People already ask their agents to get things done. When your app is agent-first, a person can ask Claude to check an order, book a class, or update a record in your app. It is done as them, with no copy and paste and no new account.
A customer asks their agent to find their last order and cancel it. The agent gets that customer's orders and no one else's.
A sales rep asks their agent to log today's calls. Each note is saved under the rep's account, with the rep's permissions.
A member asks their agent for the next open class and books a seat. The booking is made as that member, under the same rules as your site.
A manager asks their agent for the week's open tasks. A teammate's agent gets only the tasks that teammate may read.
Your words
You choose what each agent reads. A welcome opens every connection, every result can carry rich content, and each tool can name the step that comes after it.
Unified apps
Every app you build on Substrio can work with every other one. Your users sign in once and move between your apps as the same person. One app uses another app's data and functions directly, with no HTTP and no shared code, and one agent works across all of them. You choose what each app shares.
A person signs in once with Substrio, and every app connected to that sign-in lets them in without a password.
Read the docsOne app can use another app's functions and queries directly, with no HTTP and no shared code. You choose what each app shares.
Read the docsAn agent signs in once, at one app, and uses the tools of every app connected to it, as the same person.
Read the docsStart free with 1 GB, no credit card, and no time limit. Launch on Free, then grow with Standard for just $9/month.