cURL Generator MCP
An MCP (Model Context Protocol) server that turns the cURL Generator / 星轨控制台 toolbox into agent-callable tools:
- HTTP requests — send requests locally with structured params, headers, auth and bodies.
- Signed code generation — generate
cURL, Python, JavaScript, TypeScript, Node.js, Java, C#, Go, PHP and Rust code; optionally compute a Java-compatible MD5/SHA256 signature at runtime or embed the static value. - Signature placement — body, header, query string, or automatic (GET-like → query, others → body), with custom field/header names.
- GateShell bastion — password login, list authorized machines, jump into a target, execute commands, run HTTP requests from inside, upload/download files.
- Standard SSH jump host —
direct-tcpipjump execution and SFTP upload/download.
The server speaks stdio and reuses the desktop app's ~/.cURL configuration, so environments, signing keys, SSH jump hosts and target machines are shared.
Install
pip install curlgen-mcp
# or run without installing
uvx curlgen-mcp
Python 3.10+ is required. Dependencies: mcp>=1.29,<3 (both the 1.x FastMCP and 2.x MCPServer API lines are supported) and paramiko.
MCP client configuration
{
"mcpServers": {
"curlgen": {
"command": "uvx",
"args": ["curlgen-mcp"],
"env": {
"CURLGEN_CONFIG_DIR": "C:\\Users\\you\\.cURL"
}
}
}
}
CURLGEN_CONFIG_DIR is optional; it defaults to ~/.cURL. Existing desktop-app files are read directly:
| File | Used for |
|---|---|
env_configs.json |
Environments, signing keys/algorithm/field, custom variables, SSH target label |
ssh_config.json |
GateShell jump host and target machine list |
saved_requests.json |
Read-only; not used by the current tools |
Secrets are never returned by list_environments or ssh_list_targets; they are only used for the requested operation.
Tools
| Tool | Purpose |
|---|---|
list_environments |
List environment aliases, signing settings, variable names and SSH target labels |
http_request |
Send an HTTP request from the local machine |
generate_code |
Generate request code in one of ten languages |
ssh_list_targets |
List configured target machines and jump host (password masked) |
ssh_exec |
Execute a command through a standard SSH jump host |
remote_http_request |
Send an HTTP request from a remote target (transport=gateshell/ssh) |
bastion_login |
Log in to the GateShell menu |
bastion_list_hosts |
List all machines authorized on the bastion |
bastion_connect |
Enter a target machine's shell |
bastion_exec |
Execute a command on the connected target |
bastion_status |
Show login state and the selected target |
bastion_logout |
Close the bastion session |
bastion_upload |
Upload a local file to the target via base64 chunks |
bastion_download |
Download a remote file via base64 chunks |
ssh_upload |
Upload a local file via SFTP |
ssh_download |
Download a remote file via SFTP |
http_request / generate_code arguments
Both accept the same request shape:
method,url,environmentheaders,paramsbody,body_type(json/form/raw/none)auth_type(none/bearer/basic/api_key),auth_token,auth_username,auth_password,auth_headersign_enabled,sign_placement(auto/body/header/query/none),sign_field,sign_header,sign_algo,sign_keyverify_ssl,timeout,proxy,follow_redirects
generate_code additionally takes lang and sign_mode (static / runtime).
Signing compatibility
The signature string follows the Java backend used by the desktop app:
sorted(k1=v1&k2=v2&...) + "&" + "key=" + secret
- Keys are sorted case-insensitively by upper-cased name.
- Empty values,
None, and the signature field itself are excluded. - MD5 and SHA256 both return upper-case hex.
- Query params and JSON / form / raw body params are merged before signing.
sign_placement=autoputs the signature in the query string forGET/HEAD/OPTIONS, otherwise in the body.sign_headerdefaults toX-Sign;sign_fielddefaults to the environment'sparam_name(usuallysign).
Runtime signing code is generated for Python, JavaScript, TypeScript, Node.js and Java. Other languages receive the static signature value (already injected into the URL, headers or body). This keeps generated snippets runnable without adding signing logic to every ecosystem.
Runtime signing snippets read the key from the CURLGEN_SIGN_KEY environment
variable; the real key is never embedded in generated code. Set it before
running the snippet, for example:
export CURLGEN_SIGN_KEY="your-key" # PowerShell: $env:CURLGEN_SIGN_KEY="your-key"
GateShell notes
GateShell is a menu-based bastion. It does not support SSH exec and does not pass raw TCP through direct-tcpip; this server therefore drives its interactive menu:
password login → invoke_shell menu → /<ip> search → Enter → target shell
→ sentinel-wrapped command → exit code + output
The session is reused across tool calls; call bastion_logout to close it.
File transfer
- GateShell uploads: truncate the remote path, append base64 chunks, then verify size and SHA-256.
- GateShell downloads: check remote size, read one base64 stream, decode locally, then verify size and SHA-256.
- Standard SSH: SFTP with the same size and SHA-256 checks.
- Default maximum transfer size is 8 MiB (
CURLGEN_MCP_MAX_TRANSFERbytes). GateShell commands are capped at 16 KiB of payload even ifCURLGEN_MCP_CHUNK_SIZEis larger. - Local paths are restricted to
$HOMEand the current working directory by default. Override withCURLGEN_MCP_FILE_ROOTS(OS path separator,;on Windows,:on POSIX). Symlinks are resolved before the check.
Environment variables
| Variable | Default | Meaning |
|---|---|---|
CURLGEN_CONFIG_DIR |
~/.cURL |
Configuration directory |
CURLGEN_ENV |
— | Default environment alias |
CURLGEN_SIGN_KEY |
— | Override the environment signing key |
CURLGEN_SIGN_ALGO |
— | Override MD5 / SHA256 |
CURLGEN_JUMP_HOST / CURLGEN_JUMP_PORT / CURLGEN_JUMP_USER / CURLGEN_JUMP_PASSWORD |
— | Override jump host settings |
CURLGEN_TARGET_HOST / CURLGEN_TARGET_PORT / CURLGEN_TARGET_USER / CURLGEN_TARGET_PASSWORD / CURLGEN_TARGET_KEY |
— | Override target machine settings |
CURLGEN_JUMP_KEY |
— | Jump-host private key path |
CURLGEN_MCP_FILE_ROOTS |
$HOME + CWD |
Allowed local paths for transfer |
CURLGEN_MCP_MAX_TRANSFER |
8388608 |
Maximum upload/download bytes |
CURLGEN_MCP_CHUNK_SIZE |
65536 |
GateShell transfer chunk bytes (capped at 16384) |
CURLGEN_MCP_MAX_RESPONSE |
2097152 |
Maximum response bytes (local and remote, max 20 MiB) |
CURLGEN_MCP_LOG_LEVEL |
INFO |
Server log level written to stderr |
Security
This server can execute commands and transfer files on remote machines. Run it only in MCP clients you trust, protect ~/.cURL (it can contain signing keys and the jump-host password), and prefer environment-variable injection for secrets in CI. Every command is explicitly requested by the agent; no background jobs are started. Request previews and generated code intentionally include the request's own credentials (for example a bearer token) so the snippet can run; signing keys and SSH passwords are not included. Disabling TLS verification (verify_ssl=false) or using a proxy exposes traffic to interception — use only when you understand the risk.
License
MIT. Registry metadata marker: mcp-name: io.github.xiaobinger/curlgen-mcp
Metadata
Release files for curlgen-mcp 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| curlgen_mcp-1.0.1.tar.gz | 57.4 kB | Without provenance | Details for curlgen_mcp-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| curlgen_mcp-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for curlgen_mcp-1.0.1-py3-none-any.whl |
Total release size: 100.2 kB
Release files / curlgen_mcp-1.0.1.tar.gz
| Download URL | curlgen_mcp-1.0.1.tar.gz |
|---|---|
| Size | 57.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
afbbea3e3105ec41637c6bbf9b594709d80d37f6318c212a588b0cfedcab48db
|
|
BLAKE2b-256 checksum How to use checksums |
1036db211884be89f72613ef0342c17977d70c9be16627b5870c829bdb2afb7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Release files / curlgen_mcp-1.0.1-py3-none-any.whl
| Download URL | curlgen_mcp-1.0.1-py3-none-any.whl |
|---|---|
| Size | 42.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
15c81618f21b932f74f5998dd2bf71c6dd4ce522fc121ac1857e82f5dc6bcc0b
|
|
BLAKE2b-256 checksum How to use checksums |
a867f2104b6edda98aaeb59347660eb763ef76061cad99c4cbe0f4168219dc0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Security for curlgen-mcp 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.