Skip to main content
Read-only actions. The company’s contacts: its customers and suppliers, one per counterparty, with the fiscal details the person, you or a document gave once (tax ID, address, email, phone, a supplier’s IBAN). Look one up before asking for its details, and save what the person tells you. Reading an invoice or receipt with expenses from_document saves its supplier or customer too, never over what a contact already holds. Changing a contact never changes an issued invoice’s frozen customer. Each action accepts only its own fields (* required): list(limit, q, role); get(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 contacts_read for get, list. Use contacts 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 contact with the company’s invoices, income and expenses that name it, the latest hundred of each.
List the company’s contacts by name, its customers and suppliers, each with its tax ID, address, email, phone and IBAN. Look a customer or supplier up here before asking the person for its details.

​
Output

list returns matching customers and suppliers and whether the list was truncated. get returns the contact and its latest invoices, income and expenses. 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

Look for the customer

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.