Skip to main content
Read-only actions. 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): list(from, limit, q, to, type); get(id*); read(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_read for get, list, read. Use documents 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.

Read actions

These actions only read. They change nothing.
Read one document’s details by its id.
List the company’s documents, newest first, narrowed by type, words and dates.
Read one document’s file as content_base64 with its filename and content_type, at most 15 MB.

Output

list returns company documents matching the filters. get returns one document’s details. read returns content_base64, filename and content_type for its file, up to 15 MB. 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.

Declared output schema

Example

Use the actions of this tool in the order shown; its companion tool covers the other actions. These are the arguments of each call, in order.
1

Find deeds

2

Read the selected document

The first call as a request. Use an OAuth access token issued for this MCP resource and replace the example identifiers with values from your own company.