Cursor

Overview

Cursor can connect to Leapwork Play through MCP. After connecting, you can ask Cursor to perform work in Leapwork Play while it also works with your local files, repository, and other Cursor tools.

For example, you can ask Cursor:

  • Create a test case in Leapwork Play for this bug.

  • Search Leapwork Play for test cases mentioning admin.

  • Open the failing test case in Leapwork Play and start a browser session.

Cursor will use your normal Leapwork Play account, so it has the same access and permissions that you have in the product.

Before You Start

You need:

  • Cursor installed and signed in.

  • Access to Leapwork Play.

The MCP server URL looks like this:

https://mcp.leapwork.ai/mcp

Setup

Add Leapwork Play as a remote MCP server in Cursor.

Project configuration

Create or edit .cursor/mcp.json in your project:

JSON
{
  "mcpServers": {
    "play": {
      "url": "https://mcp.leapwork.ai/mcp"
    }
  }
}

Global configuration

To use Leapwork Play from any project, create or edit ~/.cursor/mcp.json with the same play entry.

If the same server name appears in both files, the project configuration takes priority.

Connect and authenticate

  1. Save mcp.json.

  2. Open Settings → Features → Model Context Protocol.

  3. Confirm that play is listed and enabled.

  4. When Cursor prompts for authentication, complete the browser sign-in flow for your Leapwork Play account.

After sign-in, Cursor should show play as connected and list its tools under Available Tools in Agent chat.

Using Leapwork Play

Once connected, ask Cursor for what you want done in Leapwork Play:

Create a test case in Leapwork Play named after a famous musician.

If Leapwork Play needs approval or clarification, Cursor will show that response and can continue the operation after you answer.

Leapwork Play uses MCP Streamable HTTP for Cursor. Long-running requests stay connected while Leapwork Play plans and performs the work, and Cursor receives the final result, approval prompt, or clarification prompt when the operation reaches that state.

Troubleshooting

If Cursor says the server failed to connect:

  • Make sure the MCP URL ends with /mcp.

  • Make sure Leapwork Play is reachable from your machine.

  • Open Settings → Features → Model Context Protocol and confirm play is enabled.

  • Reconnect or re-authenticate the play server if Cursor prompts you to do so.

To inspect connection issues:

  1. Open the Output panel in Cursor.

  2. Select MCP Logs from the dropdown.

  3. Check for connection, authentication, or timeout errors for play.

If authentication succeeds but the server still fails to connect, ask your Leapwork Play administrator to check that external MCP authentication is enabled for your Leapwork Play environment.

Current limitations

  • If a connection drops, ask Cursor to check the pending Leapwork Play request and continue from there.