Connect an agent

Connect Cursor to your boards

Cursor speaks the Model Context Protocol, and Glattice serves it over OAuth 2.1 — so the editor you already have open can read and write the board your work is tracked on. No API key, no local proxy, and no separate integration surface: it is the same REST API the Glattice web app runs on.

The endpoint

This is the MCP server URL for the environment you are reading this on. Add it as a remote MCP server and you will be sent to a browser consent screen.

https://qzhnzprxygzrglkwmxws.supabase.co/functions/v1/glattice-mcp

Adding Glattice to Cursor

  1. 1.Add the MCP server

    In Cursor’s MCP settings, add a new server and paste the URL above. Cursor handles the OAuth handshake itself — you do not need to store a secret anywhere.

  2. 2.Approve it in the browser

    Cursor opens a Glattice consent screen. Approve it, and the token that comes back carries exactly your permissions — no more.

  3. 3.Check that it worked

    Ask it to list your boards. A real answer means the handshake worked; an empty one usually means you authorised a different Glattice account.

  4. 4.Put it to work in the editor

    Filing cards from TODOs in the codebase, turning a spec into a board, or asking what is blocked before you start — all read-only until the target space is on Pro or Team, at which point it can write too.

Three things to ask it first

Reading works on every plan, so the first two need no upgrade. The third writes, which needs the target space on Pro or Team.

  • What boards do I have, and what are the axes on each?
  • Show me every card in the Blocked column of my sprint board.
  • Build me a board for Q3 launch tasks, owner by week.

Going further

What agents can doThe API reference

Frequently Asked Questions

Exactly what you can see, and nothing more. The token is scoped to your account and every request is enforced by Postgres row-level security, so an agent cannot reach a space you are not a member of even if it asks.

Reading works on every plan. Writing through MCP additionally requires the target space to be on Pro or Team, and your own role in that space has to allow it. Every write is recorded in the board’s history tagged as coming from an agent.

Remove the server in Cursor and the client stops calling. The authorisation is an OAuth grant against your account, so it carries the same lifetime as any other token you have issued.