Use AyoSpeed IDE from Claude, Cursor or the terminal

AyoSpeed IDE is not only a website. AI assistants such as Claude, Cursor and Codex can create projects, ask for builds and changes, check on them and publish, all through AyoSpeed IDE's MCP server. And the ayospeed command lets you keep a project's files in a folder on your computer, edit them in any editor and send the changes back.

Both use the same key: a sync token from your settings.

Create a sync token

1. 1

   Open Settings

   Click your avatar, choose Settings, and go to the Developer section.

2. 2

   Create a token

   Under Sync tokens, give the token a name you will recognise, like "Laptop" or "Cursor", and create it.

3. 3

   Copy it right away

   The token is shown once. Copy it now; if you lose it, revoke it and make a new one.

Connect an AI assistant over MCP

MCP (Model Context Protocol) is the standard way AI assistants use outside tools. AyoSpeed IDE's MCP server lives at your API address followed by /api/http/mcp, the same address shown under Sync tokens in Settings, plus /mcp. The assistant sends your token as a Bearer header.

claude mcp add --transport http ayospeed https://api.ayospeedide.app/api/http/mcp \
  --header "Authorization: Bearer YOUR_SYNC_TOKEN"

{
  "mcpServers": {
    "ayospeed": {
      "url": "https://api.ayospeedide.app/api/http/mcp",
      "headers": { "Authorization": "Bearer ${env:AYOSPEED_TOKEN}" }
    }
  }
}

[mcp_servers.ayospeed]
url = "https://api.ayospeedide.app/api/http/mcp"
bearer_token_env_var = "AYOSPEED_TOKEN"

Once connected, the assistant has these tools:

• list_projects and get_project: your projects, their build status, versions and live address.
• create_project: start a new project, optionally with a first prompt that starts the build.
• send_message: send a chat message, exactly as typing it in the workspace. It starts a build or a change.
• get_build_status: whether a build is still running, its progress, and AyoWizzy's last reply.
• list_versions and publish_project: see the history and put a version live.
• get_logs: recent logs from the published app, or just the problems.
• pull_files and push_files: read and write the project's files directly.

Work from the terminal

The ayospeed command needs Node.js 22 or newer. Install it (or run it without installing with npx @ayospeed/cli), then log in once with your sync token. The token is checked before it is saved, and is not shown while you paste it.

npm install -g @ayospeed/cli
ayospeed login          # paste your sync token
ayospeed whoami         # check the account and list its projects

Build and publish from the terminal

You can create a project, ask AyoWizzy for the first build or a change, follow it until it is done and publish, without opening the browser:

mkdir habit-tracker && cd habit-tracker
ayospeed create "Habit tracker" --prompt "A habit tracker with daily streaks" --link --wait
ayospeed ask "Add a dark mode toggle to the header" --wait
ayospeed pull           # bring the changed files into this folder
ayospeed publish --yes --wait

• ayospeed create <name>: create a project. --prompt starts the first build, --link links the current folder to it, --wait follows the build to the end.
• ayospeed ask "<prompt>": send a chat message, exactly as typing it in the workspace. Add --wait to see progress and AyoWizzy's reply, and --mode to choose the AI effort (auto, fast, power, or max, ultra and debug on paid plans).
• ayospeed wait: follow a build that is already running, wherever it was started.
• ayospeed versions: the project's versions, newest first, with Main, current and published marked.
• ayospeed publish: put the Main version live. It asks first; in scripts pass --yes. --wait follows it until the app is live.
• ayospeed logs --problems: the published app's recent errors.
• ayospeed open: open the project in AyoSpeed IDE.

Sync a folder with a project

To work on an existing project's files in your own editor, link a folder to it and pull:

mkdir my-app && cd my-app
ayospeed link           # pick a project from the list
ayospeed pull           # download its files

Edit the files in any editor, then send your changes back. The commands you will use most:

• ayospeed status: what changed here, what changed in AyoSpeed IDE, and what changed on both sides.
• ayospeed push: send your local changes. Changes AyoWizzy made since your last pull are kept.
• ayospeed pull: bring down changes made in AyoSpeed IDE. Your unpushed edits are kept; add --force to replace everything with the AyoSpeed IDE copy.
• ayospeed watch: push automatically every time you save a file.
• ayospeed doctor: check Node.js, the token, the connection and the folder in one go.
• ayospeed mcp: print the MCP setup above, filled in with your address.

When the same file was changed both in your folder and in AyoSpeed IDE, the more recent edit wins, and the command tells you which side was kept. Commands work from any subfolder of a linked folder, and ayospeed help <command> shows every option.

Leaving files out

node_modules, .git and dist are never synced, and neither are .env files, so local secrets stay on your computer (.env.example is synced). To leave out more, list them in a .ayospeedignore file in the linked folder, written like a .gitignore; a line like !.env.production brings a file back. Files that are not text, or are larger than 60 KB, are skipped with a warning.

The CLI keeps its own state in .ayospeed.json and an .ayospeed folder. If the folder is also a git repository, add both to your .gitignore.

Tokens in scripts and CI

Instead of logging in, set AYOSPEED_TOKEN in the environment, or pass --token to a single command. AYOSPEED_API_URL points the command at a different API address. Your saved login lives in ~/.config/ayospeed/credentials.json (%APPDATA%\ayospeed on Windows), readable only by you; ayospeed logout removes it.

Most commands take --json for output a script can read. The exit code says what went wrong: 1 for a mistake in the command or something to fix first, 2 for a missing or rejected token, 3 when AyoSpeed IDE could not be reached, 4 for a conflict or a project busy with another build.