Skip to main content
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

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:

Who can connect with OAuth

The setting that lets Members connect is on the Team settings tab of the admin console. It’s off by default.

Check or end connections

Only OAuth connections appear in these lists. To stop an API key, revoke the key (see Connect with an API key).

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. 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.
Last modified on November 4, 2026