Skip to main content

Creating MCP Servers

This guide walks you through adding Model Context Protocol (MCP) servers to the Helmet Registry.

Prerequisites​

Before adding a server, ensure you have:

  • Access to the Helmet dashboard
  • The server's repository URL or container image
  • Appropriate permissions to add servers

Adding a New Server​

Step 1: Access the Registry​

Navigate to the Registry section in the Helmet dashboard and click the "Add Server" button.

Step 2: Configure Server Settings​

Repository Server Configuration​

For Repository-based MCP servers:

  1. Server Name: Enter a descriptive name (e.g., "redis-mcp")
  2. Description: Provide a brief description of the server's purpose
  3. Repository Configuration: Configure the following:
    • Repository URL (GitHub, GitLab, etc.)
    • Link to source code repository

Container Configuration​

For containerized MCP servers:

  1. Select "Container Configuration"
  2. Provide the container image URL
  3. Configure any required environment variables

Step 3: Repository Integration​

Repository Scanning​

When you provide a repository URL, Helmet will:

  1. Clone and analyze the repository
  2. Detect MCP server configuration
  3. Identify tools, prompts, and resources
  4. Scan for potential security issues

Step 4: Review and Create​

After configuration:

  1. Review all settings
  2. Click "Create Server" to add it to the registry
  3. The server will be created in "Draft" status

Post-Creation Steps​

Automatic Security Scanning​

Once created, Helmet automatically:

  • Initiates a comprehensive security scan
  • Analyzes dependencies and vulnerabilities
  • Checks for exposed secrets
  • Validates tool implementations

Viewing Scan Results​

After scanning completes:

  1. Navigate to the server's detail page
  2. Review the scan summary
  3. Address any critical issues found
  4. Proceed to publishing when ready

Server Configuration Options​

Basic Configuration​

  • Name: Unique identifier for the server
  • Description: Purpose and functionality
  • Repository URL: Source code location
  • Container Image: For Docker-based servers

Best Practices​

Naming Conventions​

  • Use descriptive, lowercase names
  • Include the integration type (e.g., "redis-mcp", "github-mcp")
  • Avoid special characters except hyphens

Documentation​

  • Provide clear descriptions
  • Document required environment variables
  • Include usage examples in the repository

Security Preparation​

  • Remove hardcoded credentials before adding
  • Use environment variables for sensitive data
  • Ensure dependencies are up to date

Supported Repository Types​

GitHub​

  • Public and private repositories

Docker Hub​

  • Official and community images
  • Private registry support
  • Multi-architecture images

Other Sources​

  • GitLab repositories
  • Bitbucket repositories
  • Local file uploads

Troubleshooting​

Repository Access Issues​

  • Verify the repository URL is correct
  • Check access permissions for private repositories
  • Ensure network connectivity to the repository

Scanning Failures​

  • Review repository structure matches MCP standards
  • Check for missing dependencies
  • Verify Dockerfile or setup configuration

Container Issues​

  • Confirm image exists and is accessible
  • Check registry authentication if using private images
  • Verify image architecture compatibility

Next Steps​

After successfully adding a server: