Upload a source archive
Send ZIP bytes through the HCode API (filename in the query string, your credential in the Authorization header); the response includes the source upload ID for completeSourceUpload. Use createSourceUpload instead when a direct upload URL suits the client better.
Clients are told this tool can remove, overwrite or interrupt resources, or grant access. Set your client to ask before it runs it.
MCP can't carry file bytes. This tool returns the URL to send or fetch them with an HTTP client, using the same credential.
Arguments
| Name | Type | Required | Limits |
|---|---|---|---|
filename | string | Yes | At least 1 character(s) |
projectId | string | No | At least 1 character(s) |
Full input schema
{
"type": "object",
"properties": {
"filename": {
"type": "string",
"minLength": 1
},
"projectId": {
"type": "string",
"minLength": 1
}
},
"required": [
"filename"
],
"additionalProperties": false
}Example call
The params of a tools/call request. Replace the placeholder values with your own IDs.
{
"name": "uploadSourceArchive",
"arguments": {
"filename": "source.zip"
}
} Result
The same data as the API operation, wrapped as {"untrusted_data": true, "source": "uploadSourceArchive", "note": "...", "data": ...} so the model treats project content as data, not instructions.