Your apps, from Claude.
Connect Claude to your suite and ask your data, update records or build an app in plain language. It signs in as you, so it sees exactly what you see.
Four of your deals close in November, $266,400 in all:
- Northwind TradingNov 21$48,000
- Orbit StudioNov 14$126,500
- Bramble FoodsNov 19$39,900
- Pine & PartnerNov 26$52,000
Connect Claude in a minute
In Claude Code, one command adds the suite. The first call opens your browser to sign in and choose what Claude may do.
claude mcp add --transport http acme https://acme.grid82.app/mcpIn the Claude app, add https://<suite>.grid82.app/mcp as a custom connector.
What Claude can do there
Everything happens as you: the tools, the answers and the changes follow your permissions.
Ask your data
Questions across tables, answered from the rows you may read, with the tool call shown.
Change records
Updates and new records, each recorded in the app's history under your name.
Build an app
With a builder sign-in, propose tables, fields and roles, then review them in the Studio.
A brief worth giving it
"Design a client-delivery app with Clients, Projects and Tasks. Link tasks to projects and projects to clients. Consultants work on their assigned projects. Clients see only their own projects. Add an overview of overdue tasks."
Review the proposed tables and permission rules before you add real data.
Your agent can change. Your access rules stay.
Sam's rule
One permission compiler
The grid, generated pages, REST and MCP all ask the same compiler. Switching clients opens no route around it.
Narrower, never wider
At consent you choose which apps it may open and what it may do there, never more than you can.
Recorded and reversible
Every write it makes goes into the app's history with your name, and can be undone.
Connector features depend on your Claude plan and client. The agents overview and the documentation have the full surface.
Use your apps from Claude
Your permissions, in every client. Access opens from the waitlist.