
Katatan TEST
io.github.katatan-orgPublished by GitHub account katatan-orgv0.1.10Updated Oct 24, 2026
KATATAN E2E testing agent set — Playwright + KATATAN MCP integration
Overview
A local MCP server that provides an end-to-end testing agent set built on Playwright and KATATAN MCP integration.
- What you can do
- The listing gives no tool list, so capabilities come only from the short description: it presents itself as an end-to-end testing agent set combining Playwright with KATATAN MCP integration. It runs as a local process over stdio rather than as a remote endpoint. Beyond that, the description does not say which specific actions an assistant can perform with it.
- When to use it
- Consider it only if you are evaluating end-to-end testing setups that pair Playwright with a KATATAN MCP integration, and you are prepared to inspect the package yourself, since no tools or documentation are provided here.
- Requirements
- Runs as a local process on the user's machine over stdio, installed from the npm package @katatan/agents, so a Node.js runtime is needed. It requires an API key supplied through the environment variable YOUR_API_KEY. It is marked desktop only and not web executable.
Installation
In SourceWeft
- Open Katatan TEST 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
0Version history
1- v0.1.10LatestSep 16, 2026
Score
25% 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
Declare a license in the repository or the registry entry.