API Documentation

Everything you can connect to today: the RobotActions MCP server for AI assistants, and the WebDriver endpoint for Selenium and Appium tests. Both use your RobotActions account and run on real devices.

MCP Server

Add RobotActions to Claude, Cursor, VS Code or any MCP-compatible assistant as a remote connector, using this server URL:

https://mcp.robotactions.com/mcp

When your assistant asks you to authenticate, sign in with your RobotActions account. There is no token to copy. To set up a supported editor from the command line instead, run:

npx @robotactions/mcp@latest init

For CI or clients that cannot open a browser, send an API token as an Authorization: Bearer header instead.

MCP setup guide →

Selenium and Appium (WebDriver)

Point any WebDriver client at your RobotActions address with your API token in the path. No other code changes are needed; request a device with standard capabilities.

from selenium import webdriver

driver = webdriver.Remote(
    command_executor="https://<subdomain>.robotactions.com/t/<token>",
    options=webdriver.ChromeOptions(),
)

The token can also be sent as an Authorization: Bearer header if your client lets you set one. Capabilities such as the device, app and test name are listed in the capabilities guide.

• Selenium and Appium setup
• Capabilities guide

API Tokens

Create tokens in Settings → API Tokens after you sign in. A token is shown once when you create it, so copy it then. You can revoke it from the same page at any time. Treat tokens like passwords.

Results and Reports

Test sessions, videos, logs and reports appear in the RobotActions app, and your connected assistant can read them through the MCP tools. We do not currently publish a standalone REST API reference.

Plans

MCP access is included with device plans. Selenium and Appium test execution is part of the Automation plan. See pricing for details.

View pricing →