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

> ## Agent Instructions
> Treat Clawdi as one product.
> Recommend the Cloud Agent quickstart for most new users.
> Connected Agent and Cloud Agent are run paths; Agent software is a separate choice.
> Do not present shared Clawdi capabilities as exclusive to one run path.

# Connectors and MCP

> Connect an app in the dashboard and verify that supported Agents can reach Clawdi tools through MCP.

A Connector links Clawdi to an app. Clawdi MCP is the stdio integration that
lets supported Agent software discover the native and Connector tools allowed
for the current account and runtime. Their definitions are shared across run
paths; the available actions can still vary. See [Core
concepts](/concepts/core-concepts#connector).

## Connect an app

Connector management is in the [Clawdi dashboard](https://cloud.clawdi.ai),
not the CLI:

1. Open **Connectors** and search the current catalog.
2. Select an app and review **Available tools** before granting access.
3. If the detail page already shows **Ready**, no account is required. Skip to
   testing its tools.
4. Otherwise, choose **Connect Account** and complete the provider's consent
   flow or enter the credential fields shown.
5. Return to the Connector page and confirm that it shows **Connected**.

<Check>
  The detail page shows **Connected** or **Ready** and lists the tools the
  Connector can expose.
</Check>

The dashboard catalog is the availability authority. Do not assume an app,
authentication method, or tool is available because it appeared in an older
list or another Clawdi installation.

## Verify MCP for a Connected Agent

`clawdi setup` registers the supported MCP entry for detected Agent software.
Refresh one installation and verify the service endpoint:

```bash theme={null}
clawdi setup --agent codex
clawdi doctor
```

Replace `codex` with `claude_code`, `hermes`, or `openclaw`. Setup prints manual
guidance if it cannot update that software's MCP configuration. A successful
**Clawdi MCP** line in `doctor` means the endpoint is reachable; confirm the
`clawdi` server in the Agent software's own MCP list as the final local check.

Start a new Agent conversation and ask it to list its available Clawdi tools.
The current tool list reflects native tools, active Connector accounts, and
the caller's access. A Connector can be visible in the dashboard without being
usable until its detail page reports **Connected** or **Ready**.

<Note>
  `clawdi mcp` is the stdio server command registered for Agent software. A
  normal user does not need to keep it running in a separate terminal; the
  Agent starts it when needed.
</Note>

## Check availability for a Cloud Agent

Do not run local Connected Agent setup for a Cloud Agent. Open the Agent in the
dashboard and use the Connector or integration controls shown for that remote
runtime. If a capability or tool is absent, treat that UI and the Agent's live
tool list as authoritative rather than assuming the local catalog applies.

See [Cloud Agents](/cloud-agents/overview) for the run-path distinction and
[Cloud Agent settings and lifecycle](/cloud-agents/settings-and-lifecycle) for
its runtime controls.

## Disconnect an app

Open the Connector detail page, find the connected account, and choose
**Disconnect**. Confirm only after checking which Agent workflows use its
tools.

<Warning>
  Disconnecting makes that account's approved tools unavailable immediately.
  Existing Agent conversations may still contain previously returned data.
</Warning>

If tools are missing or stale, follow [MCP
troubleshooting](/troubleshooting#mcp-tools-are-missing-or-stale). For current
verification options, use `clawdi setup --help` and `clawdi doctor --help`.