Grid82
grid82.comJoin the waitlist
DevelopersOverview

Agents and MCP overview

Grid82 MCP endpoints for suites, Studio, and public docs, OAuth app selection, and the Studio Developer screen.

Grid82 implements the Model Context Protocol (MCP) over Streamable HTTP with OAuth 2.1 authentication. Every MCP connection acts strictly as the user who approved it and inherits their compiled permissions.

Studio Developer screen showing Copy setup prompt (1) and New key (2)

The Studio Developer page showing Copy setup prompt (1) and New key (2) for builder keys and MCP setup
  1. Copy setup prompt: Hands Claude, ChatGPT, Cursor, or VS Code a self-configuring OAuth prompt (https://studio.grid82.app/agent-setup.md for Studio, or https://{suite}.grid82.app/agent-setup.md for a suite).
  2. New key: Create scoped g82_ API keys for scripts, CI pipelines, and MCP clients that authenticate by bearer token.

MCP endpoints

Server URLWhat it reachesUse it for
https://{suite}.grid82.app/mcpAll apps of the suite you select during OAuth consentEnd-user agents (Claude, ChatGPT, Cursor, VS Code)
https://{suite}.grid82.app/mcp/codeCode Mode (search + execute) scoped to the selected appAgents running multi-step TypeScript scripts against an app
https://studio.grid82.app/mcpStudio tools: apps, schemas, permission rules, users, pages, workflowsBuilder agents creating or updating apps in one organisation
https://studio.grid82.app/mcp/codeCode Mode (search + execute) over the Builder APIBuilder agents scripting bulk schema or record operations
https://grid82.com/docs/mcpPublic documentation (search, fetch, list_pages)Giving any coding or research agent live Grid82 docs

Custom suite domains serve the same /mcp and /mcp/code paths directly on your domain.

One MCP server per suite

A suite exposes a single /mcp server for every app inside that workspace, so adding new apps never forces users to reconfigure their client:

  • apps_list returns every app this OAuth grant can open, together with its appId.
  • appId is accepted on every app tool (optional if the grant covers a single app, required when multiple apps are selected).
  • Masked tool schemas. tableId enumerations and record properties reflect only the tables and fields the signed-in caller may read. Tables outside the user’s roles are omitted completely.
  • Studio skills. Calling skills_list and skills_get on the Studio MCP server gives an agent the up-to-date manuals for building schemas, permissions, Interface pages, and workflows.

Read Set up your agent to connect your client in one prompt.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.