Skip to main content
Connect your AI coding assistant to Autosana for seamless documentation access and test flow management directly from your IDE.

Configuration

Replace <YOUR_API_KEY> with your key from the welcome quickstart or Settings → Integrations → API Key.
Run this command in your terminal:
After adding the configuration, restart your agent for the changes to take effect.

Verify the Connection

Once configured, test the server:
If the connection is successful, you’ll receive responses from both questions.

Available Tools

The Autosana MCP server provides comprehensive test management, debugging, and documentation access.

Flow Management

Suite Management

Hook Management

Apps & Environments

Filter apps_list with platform: "chrome-extension" to discover extension apps and their UUIDs. Use devices_list before a mobile run to discover model and os_versions values, then pass one typed device object to the run tool. If it is omitted, Autosana chooses the recommended default. iOS Simulator runs continue to use automatic device and OS defaults. Both flows_run and suites_run accept dependencies as a JSON array string for web runs:
Omit dependencies to use the web app’s attached defaults. Pass "[]" to explicitly run without extensions. An app UUID uses that extension’s active build; an object with app_build_id pins the exact build. Extension-enabled runs use Chromium, and one suite run uses the same extension loadout for every flow in its shared browser session.

Results & Debugging

read_flow_run reports the exact dependency build IDs and available extension metadata such as app/build IDs, app name, platform, source, branch, commit, and upload time.

Documentation


Example Usage

Generate E2E tests from your codebase

Increase test coverage from a PR

Debug failing tests

Create hooks for backend setup

Check test run history

Identify coverage gaps


Resources