quay

This MCP server provides programmatic access to Quay container registry APIs by dynamically discovering endpoints from Quay's OpenAPI specification and generating MCP tools for common registry operations. It exposes endpoints for manifest, organization, repository, robot, and tag related actions, and supports OAuth token authentication for protected resources. To use it, run the quay-mcp binary with the registry URL (and an optional OAuth token). Once running, you can invoke the generated MCP tools (for example to list repositories, fetch manifests, or manage tags) through the MCP host or client tooling. The server also integrates with Claude Desktop and MCPHost, allowing you to query and automate Quay interactions via natural language prompts or scripted commands. For example, you can start the server in standard mode with -url https://quay.io and then use tools like quay_listRepos, quay_getRepoManifest, and other dynamically generated endpoints exposed by the MCP layer.

Prerequisites:

• Go 1.23 or later
• Access to a Quay registry (e.g., quay.io)

Building from source:

# Clone the repository
git clone https://github.com/quay/quay-mcp-server.git
cd quay-mcp-server

# Install dependencies
make deps

# Build the application
make build

# The binary will be available at ./bin/quay-mcp

Using Make commands:

# Build the application
make build

# Run tests
make test

# Run example mode
make run-example

# Clean build artifacts
make clean

# Format code
make fmt

# Install to GOPATH/bin
make install

# Show all available commands
make help

Usage example:

# Start MCP server for quay.io
./bin/quay-mcp -url https://quay.io

# If authentication is needed
./bin/quay-mcp -url https://quay.io -token your-oauth-token

# Run in example mode to see available tools
./bin/quay-mcp -url https://quay.io -example

Tips and notes:

• The server filters exposed endpoints by tags (manifest, organization, repository, robot, tag) to present a focused set of MCP tools.
• If your Quay registry requires authentication, supply an OAuth token via the -token flag or the QUAY_OAUTH_TOKEN environment variable.
• When integrating with MCPHost or Claude Desktop, you can configure the mcpServers section to point to your local quay-mcp binary and pass credentials via environment variables.
• Ensure the OpenAPI discovery can reach Quay's API endpoints; network restrictions or API changes may require updates to the discovery logic.
• Use the Makefile targets for common development tasks (build, test, run-example, fmt, etc.).