Signadot MCP Server MCP Server
io.github.signadot/cli
Manage ephemeral environments and route traffic to local services via Signadot.
What is the Signadot MCP Server MCP server?
The Signadot MCP Server is a command-line interface that connects to Signadot to manage ephemeral environments and route traffic to local services. It enables developers to create isolated, temporary environments for testing and development workflows.
Signadot CLI provides integration with the Signadot platform for managing ephemeral environments. Use it to create temporary isolated environments, manage traffic routing to local services, and streamline development and testing workflows without affecting production systems.
How to install Signadot MCP Server
Copy-paste configuration for popular MCP clients.
SIGNADOT_API_KEYrequiredsecretSignadot API Key
Use cases
- Create and manage ephemeral development environments
- Route traffic from Signadot to local services for testing
- Test changes in isolated environments before production deployment
- Manage multiple temporary environments for parallel development
- Integrate local development with Signadot's environment management platform
Signadot MCP Server MCP server FAQ
It's a command-line interface that connects to the Signadot platform to manage ephemeral (temporary) environments and route traffic to local services, enabling isolated testing and development workflows.
The README does not specify pricing. Visit signadot.com for details on free tier availability and pricing.
Download pre-built binaries for Linux (amd64/arm64) or macOS (amd64/arm64) from the GitHub releases page, or run the install script: curl -sSLf https://raw.githubusercontent.com/signadot/cli/main/scripts/install.sh | sh
The README does not detail authentication requirements. See the CLI reference at signadot.com/docs/reference/cli for setup instructions.
The Signadot CLI is available for Linux (x86_64 and ARM64) and macOS (Intel and Apple Silicon).
Yes, you can build from source using Go 1.27.1 or later with `go build ./cmd/signadot`, though the main branch has a private dependency that may prevent building.
README (reference)
Source of truth, from the repository.
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:
curl -sSLf https://raw.githubusercontent.com/signadot/cli/main/scripts/install.sh | sh
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.1+.
The main package is in cmd/signadot:
go build ./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:orgscope (create one here), owned by an Owner of the signadot org. Since registry#1383 the registry grants theio.github.signadot/*namespace only to org Owners, and the interactivemcp-publisher login githubdevice 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.json
MCP_GITHUB_TOKEN=<pat-with-read:org> mcp-publisher login github
mcp-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.
See Also
The CLI is built on top of the Go SDK.
The CLI is built using libconnect.
Related MCP servers

Signaliz
B2B lead generation, email verification, company enrichment, and agentic GTM Ops.

SignalRaven
LinkedIn buying-intent signals, intelligence reports and delivery settings for your workspace.

ShipSwift
40+ production-ready SwiftUI components and recipes for AI-native iOS app development.

SignNow API helper tools for developers integrating e-signature workflows

SignNow MCP Server
AI-powered eSignature workflows—send documents, create templates, embed signing, and track status via SignNow API.

145+ tools across 8 databases: MySQL, PostgreSQL, Redshift, MongoDB, Redis, Kafka, and more