PlayTesterHub

com.playtesterhubPublished by playtesterhub.comOfficial publisherv1.0.0Updated Nov 8, 2026

Google Play closed testing: order 12 real Android testers for 14 days and follow the test.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

PlayTesterHub orders 12 real Android testers for a 14-day Google Play closed test and lets an assistant follow the test's progress.

What you can do
  • Order a Google Play closed testing run with 12 real Android testers for 14 days
  • Follow the status and progress of an ordered test
  • No tool list is published, so the exact actions an assistant can take are not documented beyond ordering and tracking a test
When to use it
Useful when you publish an Android app on Google Play and need to satisfy or run a closed testing requirement with real testers, and want the ordering and follow-up handled from an assistant.
Requirements
A remote server reached over streamable HTTP at the provider's endpoint; OAuth sign-in is required. No environment variables or headers are declared. A Google Play app that needs closed testing is implied.
Before you install
Ordering testers is a paid service, so expect spending and check pricing and terms before use. OAuth grants the server access to your account, and test details are shared with the provider and its testers. No tool list is published, so review what the server can do after connecting.

Installation

In SourceWeft

  1. Open PlayTesterHub in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.playtesterhub%2Fplaytesterhub/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "playtesterhub": {
      "type": "http",
      "url": "https://playtesterhub.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 8, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.