Use a connected assistant

What is it for?

A connected assistant can search the public catalog, read your applications and help prepare an app draft. It uses the permissions you explicitly grant.

It does not test Android apps for you or confirm Google Play requirements. Publishing is available only if the pilot feature is enabled on the server.

Before you start

• Have a YesWeTest member account and sign in.
• Use an MCP client that supports a remote HTTP server and a custom Authorization: Bearer header.
• The MCP pilot must be enabled on the YesWeTest server. A disabled endpoint returns 404.

Connect in five steps

1. Open Connected assistants from your profile and give the access a recognizable name.
2. Choose the shortest useful duration and only the permissions you need. Start with read access if you are unsure.
3. Create the access and copy the secret immediately; it is displayed only once.
4. Configure your compatible MCP client with the server URL and Bearer header below, then ask it to list its available capabilities.
5. Review drafts before any publication. Revoke the access from YesWeTest when you finish or if the secret is exposed.

Connection details

Enter these values in your client's secure MCP server settings. Replace the placeholder with the secret shown after access creation.

MCP server URL

https://yeswetest.org/mcp

HTTP authorization header

Authorization: Bearer <your secret>

Client menus differ. A client that cannot send a custom Bearer header cannot use this private pilot connection. Browser sign-in through OAuth is not available yet.

Choose permissions

• catalog:read — Browse public applications and categories.
• apps:read — See the applications linked to your account.
• apps:prepare — Create and update drafts before you review them.
• apps:publish — Publish a prepared app only when this feature is enabled and you granted this permission.

Advanced option: phone and local assistant

This workflow runs on your own computer. YesWeTest does not remotely control your phone.

1. On your Android phone, enable USB debugging, connect it to your computer and approve only your own computer's authorization prompt.
2. Install the official Android tools (ADB). Check the connection with “adb devices”. To view and control the screen from your computer, use scrcpy from its official source.
3. If your assistant, such as Codex with Computer Use, can access your desktop window, give it instructions limited to the mission. Watch its actions and take back control whenever needed.
4. After actually performing the test, capture the phone screen with ADB or the phone buttons. Review the image, then upload it yourself in the matching YesWeTest testing period.

MCP access and phone control are separate permissions. This workflow does not automatically validate the 14 days, Google Play Console enrollment or credits. Keep private information out of the screenshot.

Security and troubleshooting

Never paste the secret into a conversation or send it to another person. The key expires automatically and you can revoke it immediately from your account.

If connection fails, check the server URL, Bearer header, expiry and selected permissions. A 404 can mean the pilot endpoint is disabled; a 401 can mean the secret is invalid, expired or revoked.