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

# AI agents

> Give a coding agent a real place to deploy, test and tear down.

An agent that writes code needs somewhere real to run it. slipway exposes the same project
lifecycle your team uses over a first-party
[Model Context Protocol](https://modelcontextprotocol.io) server, so an agent can deploy a
change, hit the URL, read the logs and verify the fix before calling the task done.

## What an agent can do

| Capability | Detail |
| - | - |
| Deploy | Create a project from a repository and get a public URL back. |
| Inspect | List projects, services, deployments and repositories, and read a resolved spec. |
| Debug | Stream logs and run commands inside a running service, including your test suite. |
| Check capacity | Usage against the plan, and whether another deployment can start, from one call. |
| Operate | Redeploy, roll back, cancel, wait for a deploy, restart or wake a service, and tear a project down. |
| Configure | Set variables and secrets, edit a `slipway.yaml`, and change service settings, when the token's role allows it. |
| Platform | Disk snapshots, custom domains, edge settings, managed databases and object storage. |

An agent drives the same projects your team uses, through the same build, deploy and
teardown path.

## Connecting

Create a token under **Settings → MCP** in the console, then point your agent at the
endpoint with an `Authorization: Bearer` header.

```bash theme={"system"}
claude mcp add --transport http slipway https://mcp.slipway.sh/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"
```

Connection steps for Cursor and Claude Desktop, the full tool list and the role table are on
the [MCP server](/integrations/mcp) page.

## Scope the token

Every token carries a role, from viewer through admin, and each tool requires a minimum
role.

Give an agent the lowest role that lets it do its job. An agent that only inspects builds
needs `viewer`; one that writes secrets needs `admin`.

Tokens are scoped to a single organization, stored hashed, and revocable at any time. See
[roles](/integrations/mcp#roles).

## Useful prompts

Once connected, an agent can be asked directly:

* Deploy this branch to slipway and give me the URL.
* The deploy failed. Read the logs and tell me why.
* Run the test suite inside the running API service.
* Tear down the project when you are done.


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