e2e

io.github.tester-armyPublished by GitHub account tester-armyv0.23.0Updated Nov 5, 2026

Open live web and mobile app sessions from an e2e project to inspect the app and try locators.

VerifiedSTDIODesktop onlyBrowser Automation Developer Tools

Server details

Identifier: io.github.tester-army/e2e
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account tester-army for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.tester-army%2Fe2e.svg)](https://sourceweft.com/mcp/io.github.tester-army%2Fe2e?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Opens live web and mobile app sessions from an e2e project so an assistant can inspect the running app and try locators.

What you can do: Open live web and mobile app sessions from an e2e project.
Inspect the running app during a session.
Try out locators against the live app.
No individual tools are listed in the manifest, so the exact commands are not documented here.
When to use it: Useful when you are writing or debugging end-to-end tests in an e2e project and want the assistant to look at a live web or mobile session and check whether locators match the real app.
Requirements: Runs as a local process on the user's machine via npx (Node.js), over stdio. Desktop only; no web executable. An existing e2e project is needed to open sessions. No authentication, environment variables or headers are declared.

Before you install

It opens live sessions against your app, so the assistant acts on a running environment rather than a copy; point it at test or staging targets where possible. No credentials or secrets are declared, but the app under test may require its own login.

Installation

In SourceWeft

Open e2e in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

v0.23.0LatestNov 5, 2026
v0.22.0Oct 30, 2026
v0.21.3Oct 23, 2026
v0.21.2Oct 16, 2026

Score

35% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts