Signadot MCP Server
Connect to Signadot to manage ephemeral environments and route traffic to local services.
Ask AI about Signadot MCP Server
Powered by Claude · Grounded in docs
I know everything about Signadot MCP Server. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
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.18+.
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.
Prerequisite: install mcp-publisher.
./scripts/gen-mcp-server-json.sh <version> # e.g. v1.5.0 — writes server.json
mcp-publisher login github
mcp-publisher publish server.json
See Also
The CLI is built on top of the Go SDK.
The CLI is built using libconnect.
