Quickstart

Prerequisites

An Autosana account (sign up)
A mobile app or website that you want to test (duh)

A short setup walks you through it: name your workspace, then let your coding agent set things up or do it yourself and run your first flow. Afterwards, the Get started card on your home page shows what’s left. Click Restart setup on that card to go through it again.

Getting Started

Automated (Recommended)
Manual

1. Add the MCP Server

Connect Autosana with your existing account using browser sign-in. Devin currently uses the API-key setup described below.

Run in your project directory:

claude mcp add --transport http autosana https://mcp.autosana.ai/mcp

Open Claude Code, run /mcp, select Autosana, and follow the browser sign-in prompt.

In Claude, open Customize → Connectors → Add custom connector. Enter Autosana as the name and this server URL:

https://mcp.autosana.ai/mcp

Choose Connect and sign in through your browser. Your Claude account must support custom connectors; if the option is disabled, ask your workspace administrator or use another supported client.

Add Autosana to ~/.cursor/mcp.json, preserving any existing servers:

{
  "mcpServers": {
    "autosana": {
      "url": "https://mcp.autosana.ai/mcp"
    }
  }
}

Open Cursor’s MCP settings and click Authenticate beside Autosana.

Run:

gemini mcp add --transport http autosana https://mcp.autosana.ai/mcp

In Gemini CLI, run /mcp auth autosana and follow the browser sign-in prompt.

Run:

codex mcp add autosana --url https://mcp.autosana.ai/mcp
codex mcp login autosana

If you configure Codex manually, add the following to ~/.codex/config.toml, then run codex mcp login autosana:

[mcp_servers.autosana]
url = "https://mcp.autosana.ai/mcp"

A dot uses plugins installed in ChatGPT. In ChatGPT on the web, open Settings → Security and login and turn on Developer mode (Plus, Pro, Business, Enterprise, or Edu). Then open ChatGPT Plugins, select +, and create an app named Autosana with this server URL:

https://mcp.autosana.ai/mcp

Choose OAuth and approve access in your browser. Do not use an API key. In a chat, open +, choose Developer mode, and select Autosana. This connects the app in ChatGPT. It does not add a separate control inside the dot.Full walkthrough: Dots.

Grok Bot has no Settings form for a custom MCP URL, and Autosana is not in the marketplace. Send this in a Grok Bot chat:

Add a custom MCP called Autosana at https://mcp.autosana.ai/mcp

Approve the confirm card. When Grok Bot shows a sign-in link, open it and approve access. No API key is needed. Next message: @ Autosana and ask it to list or run a flow. Adding MCP in Cursor does not set up Grok Bot.Full walkthrough: Grok Bot.

In Devin, open Customize → MCPs → Add a custom MCP. Choose HTTP, not STDIO. Open Settings → Integrations → Devin to create a key, then fill in:

Server name: Autosana
Transport: HTTP
Server URL: https://mcp.autosana.ai/mcp
Authentication: Auth Header
Header key: x-api-key
Header value: <YOUR_API_KEY>

Save, then use Test listing tools. Adding MCP in Cursor does not set up Devin.Full walkthrough: Devin.

Add this under mcp_servers in ~/.hermes/config.yaml (keep any other servers). Hermes opens a browser the first time it connects:

mcp_servers:
  autosana:
    url: "https://mcp.autosana.ai/mcp"
    auth: oauth

Or run hermes mcp add --url https://mcp.autosana.ai/mcp --auth oauth autosana. Do not use --auth header — that writes Authorization: Bearer. Adding MCP in Cursor does not set up Hermes Agent.Full walkthrough: Hermes Agent.

Run:

openclaw mcp set autosana '{"url":"https://mcp.autosana.ai/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login autosana

Follow the browser sign-in prompt.

In the browser, sign in to Autosana, check the agent name and company, and click Connect. The agent can work in any workspace you can access in that company. Return to your agent and ask it to list your Autosana flows.If the authorization session ends before you approve, start a fresh connection from your agent. Do not reuse the old browser tab.Existing API-key connections continue to work. To switch one to browser sign-in, remove its x-api-key header and reconnect. Keep the key until the new connection works; revoke it only if no other integrations use it.

Note: We recommend adding the MCP server at your project root so your agent has context across your frontend and backend.

You may need to restart your agent for the changes to take effect.

2. Onboard

Tell your agent:

Onboard me to Autosana

It’ll handle CI/CD setup, test planning and creation, and more.

Step 1: Add Your App or Website

Mobile
Web

CI/CD Pipeline Integration (Recommended)

Create an API key for your CI pipeline with autosana keys create or in Settings → API Keys
Follow the setup guide to integrate with your pipeline (GitHub Actions, Fastlane, Expo EAS, etc.)
Your first build will automatically create the app in Autosana

Learn more about our CI/CD Integration →Manual UploadGet your build file ready (iOS: .zip containing your .app bundle, Android: .apk). Learn how to build your app →

Navigate to the Apps page from the sidebar
Click Create New App
Fill in app name, bundle ID, platform, and optionally an environment
Drag and drop your build file, then click Upload

CI/CD Pipeline Integration (Recommended)

Create an API key for your CI pipeline with autosana keys create or in Settings → API Keys
Follow the setup guide to integrate with your pipeline (Vercel, Netlify, etc.)
Your preview URL will automatically be registered with Autosana on every deploy

Learn more about our CI/CD Integration →Manual Setup

Navigate to the Apps page from the sidebar
Click Create New App
Enter your app name, URL, select Web as the platform, and click Create

Step 2: Create Your First Flow

A Flow is a test written in natural language that describes what you want to test.

Navigate to the Flows page
Click Create Flow

Write your flow instructions in natural language:

Open the app
Tap on the login button
Enter "test@example.com" in the email field
Enter "password123" in the password field
Tap the submit button
Verify that the home screen appears

Click Create Flow

See Writing Effective Flow Instructions for our style guide on writing effective flows.

Step 3: Run Your First Flow

Find your flow in the Flows table
Click the Play button (▶️) next to your flow
Select your app from the dropdown
Click Run Flow

Your flow will now execute on our cloud infrastructure. You’ll see real-time status updates as the flow progresses.

Step 4: View Results

Once your flow completes:

Click on the status badge (Passed/Failed) in the Flows table
View detailed results including:
- Screenshots at each step
- Actions performed by the agent
- Any errors encountered

On the Runs page, open a batch’s Preview and select View details to see its combined results. The address bar updates to a shareable batch URL. Closing the dialog restores your previous URL and filters.

Next Steps

Suites

Group related flows and run them together

Automations

Schedule flows to run on builds, daily, or weekly

CI/CD

Upload builds automatically from your pipeline

Getting Started

Core Features

Best Practices

Code-Managed Flows

Guides

Integrations

Uploading Your App

APIs

Prerequisites

Getting Started

1. Add the MCP Server

2. Onboard

Step 1: Add Your App or Website

Step 2: Create Your First Flow

Step 3: Run Your First Flow

Step 4: View Results

Next Steps

Suites

Automations

CI/CD

​Prerequisites

​When You Sign Up

​Getting Started

​1. Add the MCP Server

​2. Onboard

​Step 1: Add Your App or Website

​Step 2: Create Your First Flow

​Step 3: Run Your First Flow

​Step 4: View Results

​Next Steps

Suites

Automations

CI/CD

Prerequisites

When You Sign Up

Getting Started

1. Add the MCP Server

2. Onboard

Step 1: Add Your App or Website

Step 2: Create Your First Flow

Step 3: Run Your First Flow

Step 4: View Results

Next Steps