io.github.signadot/cli

Official

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

8 3 tools GitHub

No known CVEs

No license

Actively maintained

Last commit 3d ago

Works with most clients

Transport: stdio

3 tools · ~91 tok

Grade A · 0.0% of 200K ctx

Edit this pageView history

DevOps

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-signadot-cli": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-signadot-cli)](https://mcppedia.org/s/io-github-signadot-cli)

Read me

What io.github.signadot/cli does

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

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

70/100across 5 weighted dimensions

How we score →

0255075100

−30

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Inventory

Tools (3)

Click any tool to inspect its schema.

~91 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.signadot/cli safe to use?: io.github.signadot/cli has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.signadot/cli?: io.github.signadot/cli can be installed by cloning its GitHub repository and following the setup instructions in the README.
What can io.github.signadot/cli do?: io.github.signadot/cli provides 3 tools: Install, Build, Release. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.signadot/cli?: io.github.signadot/cli is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.signadot/cli actively maintained?: io.github.signadot/cli is actively maintained — last commit was 3 days ago. It has 8 GitHub stars.

Similar servers

Others in devops

View all →

Mcp Gitlab96

MCP server for using the GitLab API

1.6k 12

Mcp Gitlab Server92

Enhanced MCP server for GitLab: group projects listing and activity tracking

51 2

Alibabacloud Devops Mcp Server92

Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.

116 7

Komodo MCP Server91

MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI

7 11

MCP Security Weekly

Get CVE alerts and security updates for io.github.signadot/cli and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Signadot CLI

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

Please see the CLI reference for installation and usage instructions.

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.

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

Frequently Asked Questions

Is io.github.signadot/cli safe to use?

io.github.signadot/cli has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.signadot/cli?

io.github.signadot/cli can be installed by cloning its GitHub repository and following the setup instructions in the README.

What can io.github.signadot/cli do?

io.github.signadot/cli provides 3 tools: Install, Build, Release. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.signadot/cli?

io.github.signadot/cli is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is io.github.signadot/cli actively maintained?

io.github.signadot/cli is actively maintained — last commit was 3 days ago. It has 8 GitHub stars.

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.

Install

To install the CLI, run:

curl -sSLf https://raw.githubusercontent.com/signadot/cli/main/scripts/install.sh | sh

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

io.github.signadot/cli

Install in your client

What io.github.signadot/cli does

Test This Server

Why this score

70/100across 5 weighted dimensions

Security

Tools (3)

Reviews

Frequently Asked Questions

Similar servers

Discussion

io.github.signadot/cli

Install in your client

What io.github.signadot/cli does

Test This Server

Signadot CLI

Install

Build

Release

Post-release: publish to the MCP Registry

See Also

Why this score

70/100across 5 weighted dimensions

Security

Tools (3)

Reviews

Frequently Asked Questions

Similar servers

Discussion

Signadot CLI

Install

Build

Release

Post-release: publish to the MCP Registry

See Also