mcpField
S
Signadot MCP Server

Signadot MCP Server

Local
github.com/signadotCloud & Infra8Updated 4w ago
Repository

About Signadot MCP Server

Signadot CLI is a command-line interface for working with Signadot. The supplied README covers CLI installation and release procedures but does not describe the MCP tools or capabilities behind the listed server.

Key features

  1. 01Install the CLI with a script
  2. 02Select a CLI version during installation
  3. 03Build the CLI from source
  4. 04Publish releases and MCP registry entries

Use cases

  1. 01Install Signadot CLI in a target directory
  2. 02Build the CLI while testing changes
  3. 03Publish a release and its MCP registry entry

MCP support

The README describes publishing an MCP server entry to the official MCP Registry, but does not explain the server's tools or client-facing behavior.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository
Packages
mcpbsignadot-cli_mcp_linux_amd64.tar.gz
mcpbsignadot-cli_mcp_linux_arm64.tar.gz
mcpbsignadot-cli_mcp_darwin_amd64.tar.gz
mcpbsignadot-cli_mcp_darwin_arm64.tar.gz

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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:

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: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.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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.