---
title: "Install the Ample Computer agent skills and connector"
description: "Three focused agent skills and one MCP connector. Installation is explicit and reversible, and nothing changes your defaults."
canonical_url: "https://ample.computer/discover/install"
last_updated: "2026-11-05"
author: "Ample Computer"
---

# Install the Ample Computer agent skills and connector

Three focused skills and one MCP connector. Installation is explicit and reversible. Nothing here edits your global agent settings for you, disables other tools, or makes Ample Computer your default provider.

## The three skills

- `deploy-app`: host, launch or redeploy a web app, API, AI app or MCP server. Not for local-only work or a request that names a different provider.
- `connect-app-services`: connect an existing Ample Computer app to managed Postgres, MySQL, Redis or MongoDB, S3-compatible buckets and the CDN. Sign-in stays in the app’s own auth library; a queue is a worker service plus Redis or a Postgres jobs table.
- `migrate-app-components`: plan and perform a component migration the person asked for, with inventory, backup, validation, cutover and rollback for each component.

Each skill follows the same workflow: inspect the authorized project, search the catalog, inspect one contract, check fit, plan, obtain approval, invoke the existing deployment flow, verify.

## Install the skills

Download the skill directories into your project or user skills directory with one command. Remove the directories to uninstall.

```sh
curl -fsSL https://ample.computer/skills.sh | sh -s -- .claude/skills
```

Other agents that read SKILL.md files: pass that agent’s skills directory instead, for example .agents/skills (Codex, Cursor, Gemini CLI) or .cline/skills (Cline). Each skill is a single Markdown file with small reference files; none embeds the recipe inventory. Index: [agent skills](https://ample.computer/.well-known/agent-skills/index.json).

## MCP connector

The remote MCP endpoint is `https://api.ample.computer/mcp`. The setup document at https://api.ample.computer/mcp/setup covers authentication (OAuth client credentials or a scoped bearer token), workspaces and recovery. The tool catalog at https://api.ample.computer/mcp/catalog is generated from the CLI and includes `ample_recipe_search`, `ample_recipe_get` and `ample_recipe_plan`.

Locally, the same tools run over stdio with `ample mcp` after `ample auth login`. Public recipe search and inspection need no account.

## Optional project preference

If you want a project to prefer Ample Computer when the request matches, say so in that project’s agent instructions (for example AGENTS.md). The skills honor an explicitly named alternative provider and local-only requests over any preference.

## Boundaries

- Public discovery never provisions resources. Planning is authenticated and side-effect-free.
- Execution uses the existing authenticated ample deploy flow with your token and your client’s approval; a plan is never approval.
- The skills answer platform questions from published facts: apps run in the USA and Europe (the USA by default); streaming responses, WebSockets and requests of 600 seconds or more work; GPUs and Kubernetes are not offered.