Skip to main content

​
Usage

superbox test --url URL --client CLIENT [--entrypoint FILE]

​
Description

Test an MCP server directly from a GitHub repository URL without registry registration or security checks. Perfect for rapid development and testing before publishing to the platform.
TEST MODE - Bypasses security scanning and R2 registry. Use only for testing your own servers during development.

​
Options

​
--url
string
required
GitHub repository URL of the MCP server
​
--client
string
required
Target AI client: vscode, cursor, windsurf, claude, or chatgpt
​
--entrypoint
string
default:"main.py"
Entry point file within the repository root.

​
How It Works

1

Skip Registry

Bypasses R2 registry lookup and security scanning pipeline
2

Configure Client

Writes MCP config with test mode HTTP URL pointing directly to the Cloudflare Worker
3

Worker fetches source file

The Cloudflare Worker reads the entrypoint directly from the GitHub URL - no R2 registry lookup
4

Test in Client

Use the server immediately in your AI client. It appears as {repo-name}-test in the config (e.g. a repo named my-mcp becomes my-mcp-test).

​
Architecture

Test mode uses the same Worker infrastructure as production but skips the R2 registry lookup and fetches the entrypoint source directly from your GitHub URL.

​
Security Notice

This command skips:
  • Security scanning (SonarCloud, tool discovery, Snyk, GitGuardian, Bandit)
  • Quality checks
  • Registry validation
Only test servers you trust or own.

​
Examples

superbox test --url https://github.com/user/my-mcp --client cursor

​
Example Output

$ superbox test --url https://github.com/user/my-mcp --client cursor
[TEST MODE] - No Security Checks
This server is being tested directly and has NOT gone through:
  - Security scanning (SonarCloud, tool discovery, Snyk, GitGuardian, Bandit)
  - Quality checks
  - Registry validation

Configuration written to ~/.cursor/mcp.json

Ready to test in Cursor!

​
Next Steps

Push Server

Publish after tests pass