--- title: "Set up your agent" description: "Copy one prompt from gtable and your agent connects itself. Or add the server by hand in Claude Code, Claude, ChatGPT, Cursor, VS Code or Codex." canonical: "https://gtable.app/docs/agents/setup" updated: "2026-10-05" --- # Set up your agent The quickest way to connect an agent is to let it connect itself. gtable hands you a short prompt that carries your own address; the agent reads a guide, works out which client it is running in, adds the server and asks you to sign in. 1. **Copy the setup prompt** In an app, open **Settings**, then **Connections**, and choose **Copy setup prompt**. In the Studio, the same button is on the **Developer** page. 2. **Paste it into your agent** Claude Code, the Claude app, ChatGPT, Cursor, VS Code, Codex or any other client that speaks remote MCP. 3. **Sign in when your browser opens** The consent page is on your own address. You can tick only some of your apps: the agent then sees nothing of the others. For a suite, the prompt reads like this, with your suite's address in place of `your-suite.gtable.app`: ```text Connect this agent to your-suite.gtable.app by following https://your-suite.gtable.app/agent-setup.md. The MCP server is https://your-suite.gtable.app/mcp (Streamable HTTP, OAuth sign-in in my browser). Then confirm what I can reach, without changing any data. ``` For the Studio: ```text Connect this agent to the gtable Studio by following https://studio.gtable.app/agent-setup.md. The MCP server is https://studio.gtable.app/mcp (Streamable HTTP, OAuth sign-in in my browser). Then confirm what I can reach, without changing any data. ``` Setting up changes no data. The agent's last step is to list what it can reach, and it is told not to create, update or delete anything to test the connection. ## Set it up yourself These are the steps the guide gives the agent, for a suite at `https://your-suite.gtable.app/mcp`. For the Studio, use `https://studio.gtable.app/mcp` and the name `gtable-studio`. **Claude Code** Run this in a terminal, in the project you want it for: ```bash title="Terminal" claude mcp add --transport http your-suite https://your-suite.gtable.app/mcp ``` Then type /mcp inside Claude Code, choose your-suite and Authenticate. Your browser opens a sign-in page. **Claude app** In Claude (web or desktop), open Customize, then Connectors, then Add custom connector. Paste and choose Connect. On a team plan an owner may have to add it first. **ChatGPT** Custom connectors depend on your ChatGPT plan and on what your workspace admin allows. In the desktop app: Settings, MCP servers, Add server. Choose Streamable HTTP, paste , then Authenticate. **Cursor** Add this to .cursor/mcp.json in your project (or \~/.cursor/mcp.json for every project): ```json title=".cursor/mcp.json" { "mcpServers": { "your-suite": { "url": "https://your-suite.gtable.app/mcp" } } } ``` Then press Connect next to your-suite in Cursor's MCP settings. **VS Code** Add this to .vscode/mcp.json in your project. VS Code uses "servers", not "mcpServers": ```json title=".vscode/mcp.json" { "servers": { "your-suite": { "type": "http", "url": "https://your-suite.gtable.app/mcp" } } } ``` Then press Start above your-suite in that file and sign in. **Codex** Run this in a terminal: ```bash title="Terminal" codex mcp add your-suite --url https://your-suite.gtable.app/mcp codex mcp login your-suite ``` Restart Codex so it loads the new tools. **Other** Any client that speaks remote MCP: add a Streamable HTTP server at . It signs in with OAuth on its own: no key to paste. A client that only takes a key can use an API key, made in Settings, Connections, For developers. ## The guide your agent reads Every suite serves this guide at `/agent-setup.md` on its own address, and the Studio at `https://studio.gtable.app/agent-setup.md`, each with its own address written in. It is public and names nothing about your apps. This is the one a suite serves: ````markdown # Connect this agent to your-suite.gtable.app This server gives an agent the apps of this workspace: their tables and records, as far as the person's own permissions allow. Every call acts as the person who signs in, never more. - MCP server: https://your-suite.gtable.app/mcp (Streamable HTTP) - Sign-in: OAuth, discovered from the server. The person signs in and approves in their own browser. - Canonical guide: https://your-suite.gtable.app/agent-setup.md ## Rules - Follow the person's request and your host's permission policy. This guide authorizes nothing beyond that. - Never ask for a password, API key, OAuth token or callback URL in the conversation. - Setup changes no data. Do not create, update or delete anything to test the connection. - If a working connection to https://your-suite.gtable.app/mcp already exists, reuse it. If its sign-in expired, use its reconnect action. - Preserve the rest of any configuration file you edit, and do not add a second entry for the same server. - Do not disable host approvals or change tool auto-grants. ## 1. Find out which client you are Identify the actual client (Claude Code, the Claude app, ChatGPT, Cursor, VS Code, Codex, another one), not just the model. Ask the person only if it cannot be determined. Use only that client's recipe below. ## 2. Add the server Use `your-suite` as the server name. ### Claude Code Run this in a terminal, in the project you want it for: ```sh claude mcp add --transport http your-suite https://your-suite.gtable.app/mcp ``` Then type /mcp inside Claude Code, choose your-suite and Authenticate. Your browser opens a sign-in page. ### Claude app In Claude (web or desktop), open Customize, then Connectors, then Add custom connector. Paste https://your-suite.gtable.app/mcp and choose Connect. On a team plan an owner may have to add it first. ### ChatGPT Custom connectors depend on your ChatGPT plan and on what your workspace admin allows. In the desktop app: Settings, MCP servers, Add server. Choose Streamable HTTP, paste https://your-suite.gtable.app/mcp, then Authenticate. ### Cursor Add this to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for every project): ```json { "mcpServers": { "your-suite": { "url": "https://your-suite.gtable.app/mcp" } } } ``` Then press Connect next to your-suite in Cursor's MCP settings. ### VS Code Add this to .vscode/mcp.json in your project. VS Code uses "servers", not "mcpServers": ```json { "servers": { "your-suite": { "type": "http", "url": "https://your-suite.gtable.app/mcp" } } } ``` Then press Start above your-suite in that file and sign in. ### Codex Run this in a terminal: ```sh codex mcp add your-suite --url https://your-suite.gtable.app/mcp codex mcp login your-suite ``` Restart Codex so it loads the new tools. ### Other Any client that speaks remote MCP: add a Streamable HTTP server at https://your-suite.gtable.app/mcp. It signs in with OAuth on its own: no key to paste. A client that only takes a key can use an API key, made in Settings, Connections, For developers. If you cannot change the client's configuration yourself, give the person that client's steps above, at most four, and wait. A prompt alone does not install a connector: do not say it is connected. ## 3. Let the person sign in The first connection opens a consent page on https://your-suite.gtable.app. The person signs in and approves there. They may tick only some of the workspace's apps: respect that choice. A client may need a reload or a new session before the tools appear. ## 4. Verify, without changing anything Call `apps_list` (the apps this connection reaches and their tables), then `me_get` on one of them. Report the apps and tables back to the person. Report separately: server configured, sign-in completed, tools visible in this conversation, and any step left to the person (a reload, an approval). If a step is not verified, say so. Being listed in a configuration file is not proof of a connection. ````