Connect to Signadot to manage ephemeral environments and route traffic to local services.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Remote HTTPChoose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Documentation Overview
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.18+.
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: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.
See Also
The CLI is built on top of the Go SDK.
The CLI is built using libconnect.
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Signadot MCP Server
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/signadot-mcp-server)HTML Embed
<a href="https://allmcps.com/mcp/signadot-mcp-server"><img src="https://allmcps.com/api/badge/signadot-mcp-server?style=directory" alt="Signadot MCP Server on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
39Quality signal: Fair · 39/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools16/30
Adoption & activity3/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.