Your apps, from Gemini.
Use Gemini with Grid82 through an MCP-capable host or an agent that calls the REST API. The model plans the work; your permissions decide what it reaches.
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 Gemini in a minute
Point an MCP-capable host at the suite's address, or have your agent call the app's REST API with a key made inside the app.
The MCP address is https://<suite>.grid82.app/mcp. The REST API's document is generated for the key that asks, so it lists only what that key may read.
What Gemini can do there
Everything happens as you: the tools, the answers and the changes follow your permissions.
Reason over your data
Questions and summaries over the tables you may read.
Build an agent
Call the REST API from your own backend with a scoped key. Keep the key server-side.
Design the model
Ask for a schema with clear ownership fields, the basis of the permission rules.
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.
Gemini clients differ in what they can connect to; the REST API works from any of them. The agents overview and the documentation have the full surface.
Use your apps from Gemini
Your permissions, in every client. Access opens from the waitlist.