Create Server
Servers API
Create Server
Deploy a new MCP server to the SuperBox registry
POST
Create Server
Endpoint
Authentication
- Required
This endpoint requires authentication. Include your Firebase JWT token in
the Authorization header.
Request Body
string
required
Unique server identifier. Rules: lowercase letters, numbers, and hyphens only; must start with a letter; 3-50 characters. Examples:
weather-mcp, database-query-toolstring
required
Semantic version number. Format:
MAJOR.MINOR.PATCH (e.g., 1.0.0, 2.3.1)string
required
Clear description of your server’s functionality. Length: 20-500 characters
string
required
Your name or organization name
string
required
Programming language. Allowed values:
python, javascript, typescript, go, ruststring
required
Software license. Common values:
MIT, Apache-2.0, GPL-3.0, BSD-3-Clause, ISCstring
required
Main file that starts your server. Examples:
main.py, index.js, server.ts, main.goobject
required
Git repository information
object
required
Pricing configuration
object
Optional additional metadata
Response
string
"success" on success, "error" on failurestring
Human-readable confirmation message
object
The created server object (same structure as the Get Server response)
Examples
Response Examples
Deployment Process
After creating a server, SuperBox follows this workflow:1
Repository Validation
Clone the repository, verify the structure and entrypoint, and check for required files.
2
Security Scanning
Run SonarCloud, tool discovery, Snyk, GitGuardian, and Bandit (for Python servers).
3
Registry Storage
Upload metadata to R2 registry, store repository URL and configuration, and generate the server manifest.
4
Ready
The server is immediately discoverable in the registry once the response is returned.
Repository Requirements
Python Servers
Python Servers
Required files:
main.pyor specified entrypointrequirements.txtorpyproject.tomlREADME.md(recommended)
mcp package. All dependencies must be installable via pip.JavaScript/TypeScript Servers
JavaScript/TypeScript Servers
Required files:
index.js/index.tsor specified entrypointpackage.jsonREADME.md(recommended)
@modelcontextprotocol/sdk. All dependencies must be on the npm registry.Go Servers
Go Servers
Required files:
main.goor specified entrypointgo.modREADME.md(recommended)
Best Practices
Test Locally First
Test your server thoroughly before submitting to the registry
Follow Semver
Use semantic versioning: MAJOR.MINOR.PATCH
Write Good Descriptions
Clear descriptions help users understand your server’s purpose
Security First
Never commit secrets or API keys to your repository
Document Well
Include a comprehensive README with usage examples
Choose Appropriate License
Select a license that matches your intentions
Common Errors
Invalid Server Name
Invalid Server Name
Error:
name must be lowercase with hyphens onlyUse only lowercase letters, numbers, and hyphens: my-awesome-server (valid), MyAwesomeServer (invalid)Repository Not Found
Repository Not Found
Error:
Unable to access Git repositoryEnsure the repository is public and the URL is correct.Missing Entrypoint
Missing Entrypoint
Error:
Entry point file not found in repositoryEnsure the file specified in entrypoint exists in your repository root.Security Scan Failed
Security Scan Failed
Error:
Security scan detected critical vulnerabilitiesRemove hardcoded secrets/API keys, fix code vulnerabilities, and update dependencies with known vulnerabilities.Name Already Taken
Name Already Taken
Error:
Server with this name already existsChoose a different, unique name or add your username as a prefix: username-server-name