Connect your AI coding assistant to Autosana for seamless documentation access and test flow management directly from your IDE.
Overview
Autosana provides two MCP (Model Context Protocol) servers:
| Server | Purpose |
|---|
| Autosana Docs | Access Autosana documentation, CI/CD setup guides, and build assistance |
| Autosana Agent | Create, read, update, and delete test flows and suites |
With these integrations, you can:
- Access documentation for setup and CI/CD configuration
- Build your app with guided assistance
- Create test flows from natural language descriptions
- Organize flows into suites for better test management
- Update existing tests as your app evolves
- List and search your test library
Prerequisites
Before setting up the MCP servers, ensure you have:
- An active Autosana account
- An MCP-compatible AI assistant (Claude Code, Claude Desktop, Cursor, etc.)
- Your API key (for the Autosana Agent server)
Get Your API Key
To use the Autosana Agent MCP server, you need an API key:
- Log in to your Autosana account
- Navigate to Settings → Integrations → CI/CD Integration
- Copy your API key
Keep your API key secure. Never commit it to version control or share it
publicly. Treat it like a password.
Configuration
Add both servers to your MCP configuration file:
Claude CLI
Claude Desktop
Cursor
Run these commands in your terminal:claude mcp add --transport http autosana-docs https://docs.autosana.ai/mcp
claude mcp add --transport http autosana https://mcp.autosana.ai/mcp --header "x-api-key: <YOUR_API_KEY>"
Add this to: ~/claude_desktop_config.json{
"mcpServers": {
"autosana-docs": {
"url": "https://docs.autosana.ai/mcp"
},
"autosana": {
"url": "https://mcp.autosana.ai/mcp",
"headers": {
"x-api-key": "<YOUR_API_KEY>"
}
}
}
}
Add this to: ~/.cursor/mcp.json{
"mcpServers": {
"autosana-docs": {
"url": "https://docs.autosana.ai/mcp"
},
"autosana": {
"url": "https://mcp.autosana.ai/mcp",
"headers": {
"x-api-key": "<YOUR_API_KEY>"
}
}
}
}
After adding the configuration, restart your agent for the changes to take effect.
Verify the Connection
Once configured, test each server:
Test the Docs server:
What's my app's bundle ID?
Test the Agent server:
List all my Autosana test flows
If the connections are successful, you’ll receive responses from both servers.
Autosana Docs Server
The Docs server provides access to Autosana documentation and assists with app building and CI/CD setup.
Example Usage
Try asking:
- “Set up a CI/CD pipeline for my React Native app using EAS and Github Actions”
- “Build my iOS app for Autosana”
- “What’s my app’s bundle ID?”
- “How do I configure my app for Autosana?”
Autosana Agent Server
The Agent server enables full test flow and suite management directly from your IDE.
Flow Management
| Tool | Description |
|---|
flows_list | List all flows in your organization, optionally filtered by suite |
flows_read | Get details of a specific flow by ID |
flows_create | Create a new test flow with name, instructions, and optional description |
flows_update | Update an existing flow’s name, instructions, or description |
flows_delete | Delete a flow by ID |
Suite Management
| Tool | Description |
|---|
suites_list | List all test suites in your organization |
suites_read | Get details of a specific suite by ID |
suites_create | Create a new suite with flows (suites cannot be empty) |
suites_update | Update a suite’s name or description |
Example Usage
Generate E2E tests from your codebase
Crawl my repo, come up with an E2E testing strategy, and create flows in Autosana
Increase test coverage from a PR
Look at this PR and get us to 80% E2E coverage by writing flows in Autosana
Identify coverage gaps
Look at my Autosana coverage and see where we are missing tests
Resources