An Orbit app can expose selected workflows and entities as tools that an AI assistant can call through MCP. Nothing is open to agents until you turn it on.

The [Orbit app MCP overview](https://orbitapps.io/build/mcp-servers) describes the app endpoint as `/mcp`. The tools use token authentication and signed-in user scope. Each call follows your access rules.

## You choose the tools the app supplies

MCP connects an assistant to tools outside the conversation. An app MCP server supplies tools for the workflows and entities you expose.

Each table's MCP setting starts off. The available levels are **Read**, **Read and write**, and **Full**. You can also set individual actions.

Consider an example customer portal that stores service requests. If an assistant only needs to find requests, give it read access rather than permission to change or delete requests.

A workflow can also become a tool. Its description helps an agent choose the tool. Its effect states whether the workflow only reads data, changes data, or can delete data.

A request in the conversation does not create a missing tool or grant access to another customer's records. The available tools determine what the assistant can do.

## The person's access still applies

MCP tools follow the same access rules as the app's REST API. An assistant's connection does not replace those rules.

In the portal example, Alice's connection must not expose Ben's private requests. Use separate test accounts and sample records to check that boundary before you connect an assistant to customer data.

Check the records the assistant can read, not just whether the connection succeeds. For a tool that changes records, check the saved result in the app.

An assistant's description of a change is not proof that the app saved it.

[Authentication](/features/authentication) explains the difference between identity and access. [Review an app before launch](/guides/review-an-app-before-launch) covers private-record checks.

## An app server is not the Orbit builder connection

These connections serve different jobs:

| Connection | Job |
| --- | --- |
| Your app's MCP server | Let an assistant use tools exposed by your app. |
| Orbit's builder MCP connection | Let an assistant create or change an Orbit app. |

To build an app through an assistant, use [Create an app with an MCP client](/guides/create-an-app-with-an-mcp-client). Your app's `/mcp` endpoint is not a substitute for that builder connection.

## MCP tools and REST routes share the app's data

Your screens, REST API, and MCP tools read the same tables. When you change a table and deploy, all three interfaces change with it.

An MCP client uses the app's exposed tools. An HTTP client uses the app's REST routes and OpenAPI document.

Both interfaces concern your app, rather than the Orbit platform API. Use [Generated REST APIs](/features/generated-rest-apis) to understand the app's HTTP interface.

This page explains how app MCP tools relate to your data and access rules. For activation and connection controls, see the [app MCP overview](https://orbitapps.io/build/mcp-servers).