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

# Connect Zelto to Claude

> Add Zelto as a custom connector in claude.ai or Claude Desktop, sign in with your Zelto account, and work with your monitors, findings, and conversations from a Claude chat.

Zelto runs a remote [MCP server](/docs/mcp) at `https://api.zelto.ai/mcp`. Claude
(claude.ai on the web and the Claude Desktop app) can connect to it as a
**custom connector**. You sign in with your normal Zelto account, so there is no
API key to mint, copy, or rotate.

Once connected, you can ask Claude to do the work you would otherwise do in the
dashboard: list and inspect [monitors](/docs/monitors), create or edit one, read
the results it produced, open [findings](/docs/findings), and read
[conversations](/docs/conversations) and their transcripts.

## Before you start

* **A Zelto account that belongs to the organization.** Any role can connect. The
  role you hold in that organization still decides which tools work; see
  [Your role decides what you can do](#your-role-decides-what-you-can-do).
* **A Claude plan that allows custom connectors.** On Team and Enterprise plans an
  owner of your Claude organization may have to add the connector first, and then
  each person connects their own Zelto account to it.
* **The exact server URL**, with nothing added or removed:

  ```
  https://api.zelto.ai/mcp
  ```

  The same URL is shown, with a copy button, under **Settings → Integrations →
  AI agent access → Claude** in the dashboard.

## Add Zelto in claude.ai

<Steps>
  <Step title="Open the connectors settings">
    In claude.ai, open **Settings** and go to **Connectors**.
  </Step>

  <Step title="Add a custom connector">
    Choose the option to add a custom connector. Give it a name such as `Zelto` and
    paste `https://api.zelto.ai/mcp` as the server URL. Leave any advanced OAuth
    client ID or secret fields empty: Zelto registers the client for you
    automatically.
  </Step>

  <Step title="Connect">
    Save the connector, then choose **Connect**. A Zelto window opens in your browser.
  </Step>

  <Step title="Sign in and authorize">
    Sign in to Zelto if you are not already signed in (if your account has two-factor
    authentication, you are asked for the code). Then review and approve the request
    on the [authorization screen](#what-the-authorization-screen-asks).
  </Step>

  <Step title="Use it in a chat">
    Back in Claude, start a chat and make sure the Zelto connector is switched on for
    it. Try `List my monitors` or `Which findings are open for my newest agent?`.
  </Step>
</Steps>

## Add Zelto in Claude Desktop

Claude Desktop adds remote servers from the same place as claude.ai: **Settings →
Connectors**, then add a custom connector with the same name and the same server
URL as above. Approve the request in the browser window it opens, then return to the
app.

You do not edit a configuration file and you do not paste an API key. The
`mcpServers` snippet with a bearer key in the dashboard is for clients that cannot
sign in through a browser, such as [Claude Code](/docs/mcp#claude-code).

## What the authorization screen asks

When you connect, Zelto shows an **Authorize access** screen:

* **Who is asking.** `<client> wants to access your Zelto organization over MCP`,
  where the client is the name Claude registered itself with. If you did not just
  start a connection, choose **Deny**.
* **What it will be able to do.** A list under *This will allow the application to*.
  It shows exactly what the client requested, for example *Read your organization's
  data* and *Make changes to your organization's data*. See
  [Read and write access](#read-and-write-access).
* **Which organization.** If you belong to more than one, you pick one under *Choose
  an organization*. The connection is tied to that organization only; Claude never
  sees the others. To switch later, disconnect and connect again.
* **Allow or Deny.** Nothing is shared until you choose **Allow**. If you do not
  belong to any organization yet, the screen tells you to create one before connecting.

The approval is valid for ten minutes. If you leave the screen open longer, start the
connection again from Claude.

## Read and write access

Zelto has two access scopes, `read` and `write`, and `write` includes `read`. Creating
or editing a monitor, changing a finding's status, and every other change needs
`write`. Reading monitors, results, findings, conversations, and transcripts needs only
`read`.

The client asks for its scopes; the authorization screen shows them but does not let
you change them. A connection that was granted only `read` fails on a change with
`This credential is read-only and cannot call "<tool>"`. See
[Read and write scopes](/docs/mcp#read-and-write-scopes) for the full rules.

## Your role decides what you can do

A connector acts as you. It can only do what your role in the chosen organization
allows, checked on every call:

* **Any member** can read everything and run the day-to-day changes: create, edit,
  pause, and delete monitors, and triage findings.
* **Owners and admins** can additionally run the organization-level tools, such as
  inviting or removing members, changing organization settings, deleting an agent, and
  backfilling a monitor's history with an `analysisStart` date.
* **Owners only** can change another member's role.

A tool your role does not allow answers `Only an organization owner or admin can perform
this action.` instead of acting. The full list is in
[Your role decides what you can do](/docs/mcp#your-role-decides-what-you-can-do).

## Interactive cards

In Claude, some answers open as an interactive card inside the chat instead of plain
text: the findings list, a single finding, a conversation, its transcript, and its
trace. These are the [MCP Apps views](/docs/mcp#interactive-views-mcp-apps). They use
the same sign-in, role, and scope as every other tool call. If your Claude plan or
client does not render cards, Claude falls back to the matching text tools and you still
get the data.

## Disconnect

Remove the connector in Claude (**Settings → Connectors**) to stop using it. That does
not, on its own, revoke the access you granted in Zelto, so also disconnect it from
Zelto:

1. Open **Settings → MCP clients** in the dashboard.
2. Find the row for the client, which shows who authorized it, its scopes, and when it
   was last used.
3. Choose **Disconnect**.

Disconnecting ends the access immediately: the next request from Claude is refused.
Owners and admins see every connection into the organization and can disconnect any of
them; a member sees and can disconnect only their own. Access also stops on its own if
you leave the organization or your account is suspended.

Access tokens last one hour, and Claude renews them in the background. If Claude later
says the connector needs to be authorized again, choose **Connect** on it and approve
again.

## Troubleshooting

* **Claude says it cannot connect or shows `401`.** Check that the server URL is exactly
  `https://api.zelto.ai/mcp`, then remove the connector and add it again. A `401` also
  means the connection was disconnected in Zelto or has expired; connect again.
* **The authorization screen sends you to the dashboard when you press Allow.** The
  request was older than ten minutes or was already used. Start the connection again
  from Claude.
* **`Invalid redirect URI`.** Claude's saved registration no longer matches the request.
  Remove the connector, add it again, and approve once more.
* **`This credential is read-only and cannot call "<tool>"`.** The connection only has
  the `read` scope. Under **Settings → MCP clients** disconnect it, then connect again
  and check that the screen lists *Make changes to your organization's data*. If the
  screen offers only read access, ask your Zelto contact; the client decides what it
  requests.
* **`Only an organization owner or admin can perform this action.`** The tool worked;
  your role did not allow it. Ask an owner or admin to run it, or to change your role.
* **You cannot see the organization you want.** The authorization screen lists only
  organizations you belong to. Ask an owner to [invite you](/docs/settings#members--invites),
  then connect again. A connection is tied to one organization; to use another,
  disconnect and connect again and pick it.
* **The Zelto tools do not appear in a chat.** Switch the Zelto connector on for that
  chat, or start a new chat after connecting.

## Related

* [MCP](/docs/mcp) for every tool, the REST equivalents, and the other clients.
* [Monitors](/docs/monitors) for what a monitor is and how results are judged.
* [Onboard with an agent](/docs/onboarding-with-an-agent) to set up a new organization
  end to end.


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