# Connect your AI

> Give Claude, ChatGPT, Codex or Cursor access to your Tarout account by pasting one URL

# Connect your AI

Tarout runs a hosted MCP server. Paste one URL into your AI tool, approve it once
in the browser, and that tool can deploy your apps, read your logs, run SQL and
attach domains for you.

There is nothing to install and no key to copy.

```
https://tarout.sa/api/mcp
```

## The one thing to know first

Your AI does not get a free hand. The connection is issued at **operator** level:

- It can read everything and do the day-to-day work: deploy, restart, set
  environment variables, create databases, attach domains.
- Anything **destructive or anything that costs money** does not run. It stops
  and waits for you under **Agent → Approvals** in the dashboard.
- You can cut it off at any moment under **Agent → API keys**.

So it is safe to connect before you have decided how much you trust it.

## Set it up

Find your tool below. Every route ends at the same browser sign-in screen.

### Claude (claude.ai and Claude Desktop)

Settings → Connectors → **Add custom connector**, then paste:

```
https://tarout.sa/api/mcp
```

Leave the client ID and secret fields empty. Claude will send you to Tarout to
sign in and approve.

### ChatGPT

Settings → Connectors → **Create**. Paste the same URL as the server URL and
choose **OAuth**. Leave the client ID and secret empty.

### Claude Code

```sh
claude mcp add --transport http tarout https://tarout.sa/api/mcp
```

Check it with `/mcp`. The first tool call opens the browser to sign in.

### Codex

```sh
codex mcp add tarout --url https://tarout.sa/api/mcp
codex mcp login tarout
```

### Cursor

Add this to `~/.cursor/mcp.json`, then reload Cursor:

```json
{
  "mcpServers": {
    "tarout": { "url": "https://tarout.sa/api/mcp" }
  }
}
```

A remote entry takes `url` and no `type` key. Note that Cursor only keeps **40
tools active across all of your MCP servers at once** and silently ignores the
rest, so if Tarout's tools do not appear, turn off a server you are not using.

### VS Code (GitHub Copilot)

Add this to `.vscode/mcp.json`:

```json
{
  "servers": {
    "tarout": { "type": "http", "url": "https://tarout.sa/api/mcp" }
  }
}
```

### Windsurf

Add this to `~/.codeium/windsurf/mcp_config.json`, then restart Windsurf.
Windsurf calls the field `serverUrl`, not `url`:

```json
{
  "mcpServers": {
    "tarout": { "serverUrl": "https://tarout.sa/api/mcp" }
  }
}
```

### Anything else

Any client that supports remote MCP servers takes the URL directly. The endpoint
speaks Streamable HTTP and authenticates with OAuth 2.1, including dynamic client
registration, so there is nothing to pre-register.

## What you can then ask for

Plain language is enough:

- "What have I got running on Tarout?"
- "Deploy the main branch of my api repo and tell me when it is live."
- "The checkout app is throwing 502s. Read the logs and tell me why."
- "Give the marketing site a Postgres database and wire up the connection string."
- "Point shop.example.com at the storefront app and tell me which DNS records to add."
- "How much am I spending, and on what?"

## Which tools it sees

A connected chat client is offered the common tools rather than the full API,
because most clients cap how many tools they will hold and a list of several
hundred crowds out the conversation.

Nothing is out of reach. Beyond those tools, your AI can call any Tarout
capability through `tarout_call`, and it can look up what is available with
`tarout_list_procedures`. You do not need to do anything for this to work.

## If you would rather use the CLI

The connector is the fast path. Installing the CLI gives you more: a curated
local toolset, deploys from the folder you are sitting in, and credentials scoped
per project.

```sh
curl -fsSL https://tarout.sa/install.sh | sh
tarout login
```

See [the agent guide](https://tarout.sa/docs/for-ai/start) for the full picture.

## Troubleshooting

**The tools do not show up.** Most clients need a restart after the config file
changes. In Cursor, check the 40-tool limit above.

**Sign-in fails and you are a team member.** An organization member needs API
access enabled on their account before they can connect. An owner can turn this
on for you.

**It says NEEDS_APPROVAL.** Working as intended. The action is parked under
**Agent → Approvals**, waiting for you.

**You want it gone.** **Agent → API keys**, revoke the entry named after your
client. The connection dies immediately.

---

## Every Tarout agent guide

- [Start Here (Agents)](https://tarout.sa/docs/for-ai/start.md)
- [Overview](https://tarout.sa/docs/for-ai.md)
- [Deploying an app](https://tarout.sa/docs/for-ai/deploy.md)
- [Databases](https://tarout.sa/docs/for-ai/database.md)
- [Object storage](https://tarout.sa/docs/for-ai/storage.md)
- [Custom domains](https://tarout.sa/docs/for-ai/domains.md)
- [Plans and upgrades](https://tarout.sa/docs/for-ai/billing.md)
- [Troubleshooting](https://tarout.sa/docs/for-ai/troubleshoot.md)
- [Agent Onboarding](https://tarout.sa/docs/for-ai/onboarding.md)
- [CLI Reference](https://tarout.sa/docs/for-ai/cli-reference.md)
- [CLI JSON Schema](https://tarout.sa/docs/for-ai/cli-json-schema.md)

Whole corpus in one file: https://tarout.sa/llms-full.txt · index: https://tarout.sa/llms.txt
Any docs page is raw markdown at the same URL + `.md`. Short link to the entry point: https://tarout.sa/deploy.md