> ## Documentation Index
> Fetch the complete documentation index at: https://help.zarms.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Use ZARMS from AI agents (MCP)

> Connect AI agents such as Claude, ChatGPT, and Cursor to ZARMS so they can look up and create cards. How to choose a connection method (OAuth or API key), who can connect, and how to disconnect.

ZARMS supports **MCP** (Model Context Protocol, a common standard that lets AI agents work with other services). When you connect an AI agent such as Claude or ChatGPT to ZARMS, you can look up boards and cards, create cards, and write comments right from your conversation with the agent.

The connection URL is `https://app.zarms.cloud/mcp`.

## Requirements

* Your team is in its trial, or on Starter or a higher plan
* Your team is not suspended or canceled
* Your role is allowed to connect (see the table below)

Actions from AI agents or the API don't use ZARMS credits.

## Choose a connection method

| Method | Best for | Who sets it up |
| - | - | - |
| OAuth (recommended) | Apps you connect by signing in through a browser, such as Claude and ChatGPT | Each person who uses it |
| API key | Things where you paste in a key, such as a Cursor settings file or your own scripts | An Owner or Manager issues the key |

With OAuth, each person signs in with their own Google account, chooses the team to connect and the permissions (read only, or read and write), and allows the connection. Actions run with that person's permissions, and you can disconnect later from a list.

An API key is a key issued for one team. Anyone who knows the key can use it, so keep it safe.

Step-by-step guides for each app:

* [Connect from Claude](https://help.zarms.cloud/en/mcp/connect-claude.md)
* [Connect from ChatGPT](https://help.zarms.cloud/en/mcp/connect-chatgpt.md)
* [Connect from Cursor](https://help.zarms.cloud/en/mcp/connect-cursor.md)
* [Connect with an API key](https://help.zarms.cloud/en/mcp/api-keys.md)

## Who can connect with OAuth

| Role | OAuth connection |
| - | - |
| Owner | Yes |
| Manager | Yes |
| Member | Only if an admin turns on **Allow regular members to connect via MCP OAuth** |
| Guest | No |

The setting that lets Members connect is on the **Team settings** tab of the [admin console](https://help.zarms.cloud/en/admin/admin-console.md). It's off by default.

## Check or end connections

| What you want to do | Where to go | Who can do it |
| - | - | - |
| See or disconnect apps you connected | **Settings** → **MCP connections** in the right-hand navigation | The person who connected |
| See or disconnect everyone's connections | **Team settings** tab in the admin console → **Manage member MCP connections** | Owner, Manager |

Only OAuth connections appear in these lists. To stop an API key, revoke the key (see [Connect with an API key](https://help.zarms.cloud/en/mcp/api-keys.md)).

## When the connection stops working

Even if you're connected, the connection stops working when:

* Your team's plan changes to Basic (including when the trial ends)
* Your team is suspended or canceled
* Your access is suspended, you become a Guest, or the setting that allows Members to connect is turned off
* You or an admin disconnects the app, or the API key is revoked

## Settings the agent can change

Besides boards and cards, an agent can read and change these settings.

| Settings | Who can use it | Scope |
| :- | :- | :- |
| Team settings | Owners and Managers | Team name, time zone, color, card status labels, card creation defaults, and the switches for permissions and integrations |
| Personal settings | The person who connected | Notification settings and the setting for registering cards by email (My Board) |

An agent cannot change billing and plans, referrals, the notification email, Google Drive settings, the monthly AI limit, team deletion, API key and MCP connection management, or the newsletter subscription. Use the screens for those. When you want to change a permission switch, tell the agent exactly what to change.

## Card descriptions written by agents

When an agent creates a card or rewrites its description, the description is first saved on the card, then written to the card's Google Doc a little later. It's only written to a doc whose body is still empty.

When an agent reads a card, the doc body it sees is a copy that ZARMS pulls in regularly. Very recent changes may not be included yet.

For technical details (available tools and endpoints), see the [ZARMS API documentation](https://app.zarms.cloud/api-docs).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.