Skip to main content
Melso Agents is available only internally or by private invitation. Agents-specific features require existing access. For the autónomo fiscal service, see Get started.
Prepare a version, then PUT bytes with returned scoped tickets and finalize. An app (kind app, the default) sends build/source ZIP byte sizes (max 100 MiB each). A file (kind file) sends file_name and build_size_bytes, no source, and PUTs the raw file. New artifacts require title and explicit Company/Area scope; existing apps require artifact_id and expected_revision. Finalize requires artifact_id, version_id and current expected_revision. Use separate stable request IDs per phase; deploying never publishes. Availability: Autónomo / Empresa / Agents invitation. Catalog: Advanced (tools_search, then tools_call). The live catalog is authoritative: company type, membership, plan, connected apps and execution context can narrow this contract. Understand access.

Input

Agents / Autónomo / Company schema

Output

The deployed artifact/version receipt and access information. Inspect its status before sharing a link. The result uses MCP content blocks; JSON payloads are encoded in text and may also appear in structuredContent. Check isError before reading a success payload. The server does not currently declare an outputSchema, so treat additional fields as extensible. Result handling.

Example

Use an OAuth access token issued for this MCP resource (a Run token for Run-only tools). Replace example identifiers with values from your own account. Write actions change data. First discover artifacts_deploy with tools_search and confirm that the live schema permits these arguments.