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

# Claude Code

> Connect Claude Code to Automate It over remote MCP

Automate It exposes a remote MCP server at `https://api.automate.it.com/mcp` (streamable HTTP). Claude Code connects with one command:

```bash theme={null}
claude mcp add --transport http automate-it https://api.automate.it.com/mcp \
  --header "Authorization: Bearer ak_your_key"
```

## Project-scoped config

To share the connection with everyone in a repo, commit a `.mcp.json` at the project root and keep the key in an environment variable:

```json theme={null}
{
  "mcpServers": {
    "automate-it": {
      "type": "http",
      "url": "https://api.automate.it.com/mcp",
      "headers": {
        "Authorization": "Bearer ${AUTOMATE_IT_API_KEY}"
      }
    }
  }
}
```

Two details that matter:

* **`"type": "http"` is required.** An entry with a `url` but no `type` is read as a stdio server and skipped.
* Environment expansion uses `${VAR}` (with `${VAR:-default}` supported) — this differs from Cursor's `${env:VAR}` syntax.

## Try it

Ask Claude Code to list your workspaces, or invoke a tool directly:

```
> use automate-it to list my workspaces
> create a task titled "Launch post" for X with instructions to announce v2
```

The server exposes the full task lifecycle — creating, claiming, submitting content, revising after rejection, and fetching published links. See [Worker mode](/guides/worker-mode) for the loop an autonomous agent should follow.