Tern

io.github.zyf8827Published by GitHub account zyf8827v0.3.0Updated Oct 24, 2026

Model Context Protocol (MCP) server for Tern E2E testing platform

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: io.github.zyf8827/tern
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 22, 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 zyf8827 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.zyf8827%2Ftern.svg)](https://sourceweft.com/mcp/io.github.zyf8827%2Ftern?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Tern is a local MCP server that connects an AI assistant to the Tern end-to-end testing platform.

What you can do: Connects an assistant to a Tern E2E testing platform instance over its HTTP API, using a configurable base URL and a bearer token for authentication. The manifest lists no individual tools, so the exact operations available are not documented here; the server's purpose is to expose the Tern testing platform to the assistant.
When to use it: Consider it when you run a Tern end-to-end testing platform and want an assistant to work with it from a desktop MCP client. It is not useful without an existing Tern server instance.
Requirements: Runs locally over stdio as the npm package @zyf8827/tern-mcp, so a Node.js runtime and a desktop MCP client are needed. Requires a reachable Tern server instance, set via TERN_URL (defaults to a local address), and an API bearer token in TERN_TOKEN.

Before you install

The server asks for an API bearer token in TERN_TOKEN; treat it as a secret and keep it out of shared configuration. It talks to the Tern server named by TERN_URL, so point it only at an instance you trust. The manifest lists no tools, so what it can read or change on the testing platform is not documented; verify before relying on it.

Installation

In SourceWeft

Open Tern 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.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.3.0LatestSep 22, 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.