# Agents over MCP

The Fogpipe Cloud API is also a remote MCP server, at:

```
https://api.cloud.fogpipe.com/mcp
```

An agent with no shell, such as claude.ai or Claude desktop, operates the
platform through it. An agent with a shell can use `fpcloud` instead.

## Connecting Claude

1. In Claude, open **Settings → Connectors** and add a custom connector.
2. Paste the URL above.
3. Claude opens the Fogpipe Cloud sign-in page. Sign in as you do for the console.

Nothing else is configured. The connector has no API key, and Fogpipe Cloud has no
setting to turn it on.

Claude Code takes the same URL:

```bash
claude mcp add --transport http fogpipe-cloud https://api.cloud.fogpipe.com/mcp
```

## What the agent can do

There is one tool per API route, named after it, such as `get_orgs_orgID_projects` or
`post_apps_appID_deploy`, with a plain title such as "Deploy an app". A read is
marked read-only, so a client can let it run without asking you. Every other
tool is marked as one that changes something, so a client asks you first.

The agent acts as you. It reaches exactly what your bindings reach, and every
call is checked, limited and audited like one from the CLI. Your role on a
project decides what the agent may change there.

Some routes have no tool:

- operator and platform-internal routes
- interactive streams: `app exec`, `db connect` and following logs. Read logs
  over a window instead.
- browser sign-in routes

## Signing out

Remove the connector in Claude. The sign-in lasts as long as a CLI login.