Connect an agent

Connect Claude to your boards

Glattice runs a remote Model Context Protocol server behind OAuth 2.1, which is exactly what Claude’s custom connectors expect. Add the URL, approve the consent screen, and Claude can read your spaces and boards immediately — with your permissions, enforced by the database rather than by trust.

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 Claude

  1. 1.Add it as a custom connector

    In Claude’s settings, add a custom connector or remote MCP server and paste the URL above. There is no API key to generate and no configuration file to edit.

  2. 2.Approve it in the browser

    Claude opens a Glattice consent screen. Sign in if you are not already, review what is being granted, and approve — the token that comes back is scoped to your account.

  3. 3.Check that it worked

    Ask Claude what spaces you have. It should call search_spaces and come back with the real list. If it comes back empty, you are signed into a different Glattice account than the one you authorised.

  4. 4.Give it something to do

    Reading works on every plan. If your target space is on Pro or Team, Claude can also create boards, move cards and set dates — and everything it does lands in the board’s history tagged as an agent write.

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 Claude 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.