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

# Connect your agent with MCP

> Add floo's hosted MCP server to Claude Code, Claude, Codex, Cursor, or VS Code and sign in with OAuth.

floo's MCP server is hosted at `https://api.getfloo.com/mcp`. It speaks Streamable HTTP and signs you in with OAuth, so there is no key to copy. Every tool calls the same `/v1` API as the CLI, with your account's permissions.

## Claude Code

Install the floo plugin. It adds the MCP server and the floo skill together:

```
/plugin install floo --marketplace getfloo/floo-cli
```

Or add only the server:

```bash theme={null}
claude mcp add --transport http floo https://api.getfloo.com/mcp
```

Run `/mcp` in Claude Code, pick `floo`, and approve the sign-in in your browser.

## Claude (claude.ai and desktop)

In **Settings → Connectors**, choose **Add custom connector**, name it `floo`, and enter `https://api.getfloo.com/mcp`. Claude opens floo's sign-in when you connect.

## Codex

```bash theme={null}
codex mcp add floo --url https://api.getfloo.com/mcp
codex mcp login floo
```

## Cursor

Add to `.cursor/mcp.json` in the project, or `~/.cursor/mcp.json` for every project:

```json theme={null}
{
  "mcpServers": {
    "floo": { "url": "https://api.getfloo.com/mcp" }
  }
}
```

## VS Code

Add to `.vscode/mcp.json`:

```json theme={null}
{
  "servers": {
    "floo": { "type": "http", "url": "https://api.getfloo.com/mcp" }
  }
}
```

## Use an API key instead of OAuth

For CI or a headless agent, send a floo API key as a bearer token. Create one under **API keys** at [app.getfloo.com/settings](https://app.getfloo.com/settings).

```bash theme={null}
claude mcp add --transport http floo https://api.getfloo.com/mcp \
  --header "Authorization: Bearer $FLOO_KEY"
```

## What the sign-in grants

Approving the sign-in creates an API key named `MCP: <client name>` with the highest scope your role allows. It appears under **API keys** at [app.getfloo.com/settings](https://app.getfloo.com/settings); revoke it there to disconnect the client. Org roles and approval policies still apply to every call.

## Tools

| Tool | What it does |
| - | - |
| `list_orgs`, `list_apps` | Your orgs and the apps in one |
| `create_project` | Create an app with a floo-hosted repository; its first deploy starts at once |
| `create_git_token` | A short-lived git password for that repository |
| `create_app`, `begin_github_setup`, `poll_github_setup`, `select_github_installation`, `connect_github` | Create an app and connect a GitHub repository you already have |
| `list_deploys`, `get_deploy`, `list_deploy_steps`, `create_deploy` | Find, wait on, and start deploys |
| `get_logs` | Runtime logs |
| `set_env_var`, `restart_app` | Set a variable or secret and apply it |
| `list_releases`, `promote_app`, `rollback_deploy` | Releases, promotion, and rollback; the last two are marked destructive |
| `get_spend_cap`, `get_paygo_balance` | Spend cap and remaining credit |
| `search_api`, `read_api`, `write_api` | Find and call any other `/v1` operation |

`get_deploy` waits up to 25 seconds per call when you pass `wait`. Call it again until the deploy is `live` or `failed`.

For the full deploy loop, give your agent [getfloo.com/agents.md](https://getfloo.com/agents.md). The MCP tools are the calls it names.


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