Skip to content
Sign inStart for free

MCP

Connect a coding agent (Claude Code, Codex, Cursor, Windsurf, Claude or any MCP client) to LCTester, so it can write and run your tests and read why one failed.

Connect

In LCTester, open the account menu at the bottom of the sidebar and choose MCP. The page shows your server URL (your LCTester address followed by /mcp) and the steps below with it filled in, ready to copy.

One command for every client

npx add-mcp@2 --global --name lctester https://<your LCTester address>/mcp

Finds the coding agents on your machine (Cursor, VS Code, Windsurf, Claude Code, Codex and more) and lets you pick which ones to connect. Drop --global to set it up for one repository instead.

Claude Code

claude mcp add --transport http lctester https://<your LCTester address>/mcp

Then run /mcp inside a session to sign in.

Codex

codex mcp add lctester --url https://<your LCTester address>/mcp

Then run codex mcp login lctester to sign in.

Cursor

On the MCP page, Add to Cursor opens Cursor and installs it, if Cursor is on this machine.

Windsurf (Devin Desktop)

In Cascade, open the … (Actions) menu and choose Open MCP config file (~/.config/devin/mcp_config.json). Add this, save, then refresh the MCP list in Cascade to sign in.

{
  "mcpServers": {
    "lctester": {
      "serverUrl": "https://<your LCTester address>/mcp"
    }
  }
}

Claude Desktop and claude.ai

Open Customize → Connectors, choose + Add → Add custom connector, and paste the server URL above. On Team and Enterprise plans an owner adds it first under Organization settings → Connectors.

Sign in

No API key is needed. The first time the agent calls LCTester, it opens a browser where you sign in with your LCTester account, choose the team it works in, and allow access. The agent works only in that team, only while you are a member, and never beyond your role.

What agents can do

  • Read your projects, environments, tests, groups and test account names.
  • Create and change tests and groups.
  • Run a test, a group or a discovery run, and follow it until it finishes.
  • Read what happened at each step, a short-lived link to the recording, and the issues found across runs.
  • Confirm a report a run left for you to review as a bug, which files it as an issue and tells the team. Only a signed-in person can dismiss a report.

Agents cannot delete anything, manage members or change billing. Every change they make is recorded in the team’s audit log.

Revoke

The MCP page lists your connected agents under Your connected agents. Revoking one stops it on its next call; it has to sign in again to come back. Resetting your password or leaving the team stops them too.