Signadot MCP Server

io.github.signadotPublished by GitHub account signadotvv1.9.0Updated Oct 24, 2026

Connect to Signadot to manage ephemeral environments and route traffic to local services.

VerifiedSTDIODesktop onlyCloud & Infrastructure Developer Tools

Server details

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

Overview

AI-generated overview

Signadot MCP server that lets an assistant manage ephemeral environments and route traffic to local services from the desktop.

What you can do: Manage Signadot ephemeral environments and their lifecycle
Route traffic to local services through Signadot sandboxes
Work through the Signadot CLI, which is built on the Signadot Go SDK and libconnect
When to use it: Useful when you develop against Kubernetes-hosted services and want an assistant to create or adjust Signadot sandboxes and send traffic to services running on your machine.
Requirements: Runs as a local process on the desktop (macOS or Linux builds provided); requires a Signadot account and the SIGNADOT_API_KEY environment variable; network access to Signadot.

Before you install

The server needs a Signadot API key, which is a credential granting access to your Signadot organization; environment and traffic-routing changes affect shared test infrastructure, so review actions before they run.

Installation

In SourceWeft

Open Signadot MCP Server 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

Signadot CLI

This is the source repository for the Signadot command-line interface.

Please see the CLI reference for installation and usage instructions.

To file an issue, please use our community issue tracker.

NOTE: Starting next release, and hence in the main branch, this repository has a dependency on a private repository, and hence building or running from source will not work. Previous releases should continue to work.

Install

To install the CLI, run:

By default, the script will install the latest version at /usr/local/bin/signadot. The target version can be selected by setting the SIGNADOT_CLI_VERSION variable, while you can specify the install directory with SIGNADOT_CLI_PATH.

Build

To build the CLI from source, such as to test changes, you'll need Go 1.27.3+.

The main package is in cmd/signadot:

Release

To release the CLI, you can use the release Github action. Push a new tag that matches the format v[0-9]+.[0-9]+.[0-9] and it will push new release artifacts and update brew.

Post-release: publish to the MCP Registry

After the GitHub release artifacts are live, publish the MCP server entry manually. goreleaser does not yet support the fileSha256 integrity field required by the MCP registry for mcpb packages.

Prerequisites:

install mcp-publisher
a classic GitHub PAT with only the read:org scope (create one here), owned by an Owner of the signadot org. Since registry#1383 the registry grants the io.github.signadot/* namespace only to org Owners, and the interactive mcp-publisher login github device flow cannot read org roles — logging in with a PAT is what makes org publishing work.

./scripts/gen-mcp-server-json.sh <version>   # e.g. v1.8.0 — writes server.jsonMCP_GITHUB_TOKEN=<pat-with-read:org> mcp-publisher login githubmcp-publisher publish server.json

./scripts/gen-mcp-server-json.sh <version>   # e.g. v1.8.0 — writes server.jsonMCP_GITHUB_TOKEN=<pat-with-read:org> mcp-publisher login githubmcp-publisher publish server.json

The script writes the v-prefixed tag (e.g. v1.8.0) as the version in server.json. Don't hand-edit it to the bare form — the registry treats 1.4.0 and v1.4.0 as distinct versions, and mixing the two has created duplicate entries in the past.

This covers the official MCP registry only. For getting the MCP server listed in other directories (Claude Desktop extensions, Docker MCP Catalog, and others), see docs/mcp-distribution.md.

Tools

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

Version history

vv1.9.0LatestOct 2, 2026
vv1.8.0Sep 16, 2026

Score

50% 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
License10 pts