linktest-mcp-server

Automate Google Play closed testing with AI. Skip the hassle of finding 12+ testers and waiting 14+ days — just tell your AI to handle it.

The Problem

To publish on Google Play, you need:

• 12+ testers opted in to your closed testing track

• 14+ days of continuous testing

Finding testers, getting them to opt in, and keeping them active for 2+ weeks is the biggest bottleneck for indie developers.

The Solution

LinkTest runs your app on 12+ real Android devices for 14+ days — automatically. Just tell your AI:

"Run closed testing for my app com.example.myapp"

That's it. $5 per order. No subscriptions. No tester recruitment.

Quick Start

1. Get your API token

Sign up at linktest-prod.web.app and copy your token from Settings.

2. Install

Works with any MCP-compatible AI client — Claude, Cursor, Windsurf, VS Code (Copilot), Cline, Continue, and more.

Add to your config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "linktest": {
      "command": "npx",
      "args": ["-y", "linktest-mcp-server@latest"],
      "env": {
        "LINKTEST_API_TOKEN": "your-token-here"
      }
    }
  }
}

claude mcp add linktest -s user -e LINKTEST_API_TOKEN=your-token-here -- npx -y linktest-mcp-server@latest

Add to .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "linktest": {
      "command": "npx",
      "args": ["-y", "linktest-mcp-server@latest"],
      "env": {
        "LINKTEST_API_TOKEN": "your-token-here"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "linktest": {
      "command": "npx",
      "args": ["-y", "linktest-mcp-server@latest"],
      "env": {
        "LINKTEST_API_TOKEN": "your-token-here"
      }
    }
  }
}

Any client that supports the Model Context Protocol can use this server. The config is the same:

• Command: npx -y linktest-mcp-server@latest

• Environment: LINKTEST_API_TOKEN=your-token-here

3. Start testing

Just tell your AI:

"I need to run Google Play closed testing for my app. The package name is com.example.myapp."

The AI will guide you through the entire process automatically.

Tools

Workflow

The AI handles this automatically, but here's what happens:

1. linktest_testers     → Get emails, register in Play Console
2. linktest_validate    → Check opt-in link
3. linktest_verify      → Confirm device access (takes ~30s)
4. linktest_order       → Create order → pay $5
5. linktest_status      → Monitor progress
6. linktest_screenshots → Visual confirmation

Example Prompts

Pricing

$5 per order — one-time payment, no subscription.

Each order includes:

• 12+ real Android devices

• 14+ days of daily app execution

• Daily screenshots for verification

• Free retry if rejected by Google Play (1 per order)

• Automatic management — no manual work needed

How It Works

1. You register LinkTest tester emails in your Google Play Console

2. You pay $5 per app

3. LinkTest installs your app on 12+ real Android devices

4. Devices run your app daily for 14+ days

5. Screenshots are captured daily so you can verify

6. Done — your closed testing requirement is met

Troubleshooting

MCP not loading?

If npx is installed at a non-standard path (e.g., via nvm or .local), change "command": "npx" to the full path:

which npx   # Find your npx path, then use it in the config

Better AI guidance

Add this to your Claude system prompt or CLAUDE.md for step-by-step order guidance:

When using LinkTest tools, always read the resource "linktest://workflow-guide" first to follow the correct order.

Requirements

• A Google Play Developer account

• An app with a closed testing track set up

• Node.js 18+

Environment Variables

Links

• Dashboard — Manage orders and settings

• npm — Package page

License

MIT