Add solvethree MCP to Cursor

By solvethree4 min read

Add solvethree to .cursor/mcp.json for one project or ~/.cursor/mcp.json for all projects. The server runs locally over stdio; there’s no hosted MCP URL to enter. Cursor can request solutions, but the MCP server doesn’t drive a browser or fill forms.

On this page

Configure the local MCP server

  1. 1.

    Set the environment variables

    Set SOLVETHREE_API_KEY to your workspace API key and SOLVETHREE_PROXY to the proxy you’ll use for solving and submission. Make both available to the process that launches Cursor. Don’t put literal credentials in a project configuration.

  2. 2.

    Choose the configuration file

    Use .cursor/mcp.json for project-specific setup or ~/.cursor/mcp.json for user-wide setup. A project entry named solvethree overrides a global entry with the same name.

  3. 3.

    Add the server entry

    Use the configuration below. If the file already contains other servers, add solvethree inside its existing mcpServers object rather than replacing the file.

Cursor · launch with the host environment
{
  "mcpServers": {
    "solvethree": {
      "command": "npx",
      "args": [
        "--yes",
        "--package=https://solvethree.com/downloads/solvethree-sdk-0.1.0.tgz",
        "solvethree-mcp"
      ]
    }
  }
}

This starts solvethree-mcp from the official SDK download using npx. The configuration inherits Cursor’s environment; it doesn’t depend on environment-variable interpolation inside the JSON.

Restart Cursor and inspect the tools

Fully quit Cursor, then relaunch it from an environment containing both variables. Exporting variables in a terminal doesn’t update an already-running GUI.

Inspect Cursor’s MCP tools and MCP Logs output. The server exposes solvethree_capabilities, solvethree_create_recaptcha, solvethree_create_kasada, solvethree_create_tmpt, and solvethree_get_task. Call solvethree_capabilities first to inspect the available operations.

The server doesn’t start.

Read MCP Logs for the startup error.

Try this: If Cursor can’t find npx, make it available on Cursor’s PATH and restart Cursor.

The server reports missing environment variables.

Check the environment that actually launched Cursor, not just your current terminal.

Try this: Set both variables there, fully quit Cursor, and relaunch it.

Cursor uses an unexpected configuration.

Look for a solvethree entry in both configuration files.

Try this: Update or remove the project entry if you intended to use the global one.

For Cursor’s configuration interface, see its official MCP documentation.

Request a reCAPTCHA solution

  1. 1.

    Confirm the site profile is active

    In Site profiles, configure the intended hostname, capture action, and reCAPTCHA type. Confirm that the profile is active before requesting a solve. Passing a hostname and action to the tool doesn’t create a profile. See site profile setup for the capture process.

  2. 2.

    Call the reCAPTCHA tool

    Have Cursor call solvethree_create_recaptcha with site, action, and a unique requestId. site is the hostname, not a page URL. recaptchaType defaults to enterprise-v3; waitMs is optional. The tool reads its single proxy from SOLVETHREE_PROXY, so don’t add a proxy argument, type, or url.

  3. 3.

    Follow the task to a terminal status

    If the task is pending or solving, use solvethree_get_task to check it again. Only ready contains a usable solution. If it is failed, stop polling and inspect errorCode and error before deciding what to change.

Keep the requestId if creation times out. Each create call makes at most one task, and repeating the same request ID with the same inputs recovers the existing task. Changing the inputs while reusing that ID conflicts. Don’t generate a new ID merely because the first response was lost.

Submit the solution from your application

A ready task is where the MCP server’s work ends. Your application must submit the returned reCAPTCHA token to the intended target. Use the returned userAgent and secChUa identity with the same proxy configured for the solve. Switching proxies or mixing in an unrelated browser identity can break the request.

Keep the solution type straight if you use the other tools: Kasada returns a headers object to apply together, while TMPT returns a raw tmpt cookie value. Neither is a reCAPTCHA token.

Cursor receives private solution data through the tool response. A ready result means a solution was generated—not that the target accepted your application’s request. If submission fails, inspect the outgoing token or cookie, identity, and proxy before paying for another solve.

Run your first task.

Start with $5 in workspace credit.

Create a workspace