Skip to main content
The company’s documents in one place, wherever Melso keeps them: invoices it issued, quotes, expenses (received invoices and tickets), tax returns and their AEAT receipts, the company’s own records (escrituras, estatutos, NIF, modelo 036/037, alta en el RETA, poderes, certificado de titularidad bancaria), contracts and others. They come from the files stored for the company, the expenses and income it recorded, the invoices it issued and what Melso’s professionals delivered in its Gestiones. list finds them newest first by type, words (q) and dates; get reads one; read returns its file as content_base64. save keeps a file as a document with its type: a client that keeps files reserves it with upload, PUTs its bytes to upload_url and saves it with upload_id. Saving the same upload again keeps one document. No action changes or deletes a document. Each action accepts only its own fields (* required): upload(filename*, content_type*, size_bytes*); save(type*, attachment_id, date, description, title, upload_id). Availability: Autónomo / Empresa. Access: Live in the Melso app and over MCP for a signed-in person. Where the partner REST API covers the same area, that path is private beta until Melso enables your account. See Access and pricing. The live tool list is authoritative: the company’s plan and your role can narrow this contract. Understand access.

When to use

Use documents for save, upload. Use documents_read for the companion actions. The live tool list determines availability.

Input

Actions

The tool’s schema combines the fields of every action. Each action accepts only its own fields below; send action with them.

Write actions

These actions change data. The server lists them only with a plan that includes the tools.
Keep a file as one of the company’s documents: one sent or built in the Melso chat (attachment_id), or one PUT through upload (upload_id).
Reserve the upload of a local PDF or image of at most 15 MB: PUT its exact bytes to upload_url with the returned headers, then call save with upload_id.

Output

upload returns an upload_id, the upload_url and headers for a PUT. save keeps the uploaded file with its type and details. Saving a document does not issue an invoice or file a return. 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. When the server declares an outputSchema, it is reproduced below. Check the action result and its declared fields before reporting success.

Example

Use an OAuth access token issued for this MCP resource and replace the example identifiers with values from your own company. Write actions change data.