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.
tools/list).
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
Managed run / agents / Managed run / company / Managed run / freelancer schema
Actions
The family schema combines fields for discovery. Each action accepts only its own fields below; addaction when calling the family.
delete
delete
Delete a Vault item. Its owner or a company admin can delete it.OAuth-only.
list
list
List the Vault items you can use: logins, cards, text secrets and files, with the variable each Run receives. Values are never returned.
request
request
Ask a person to save a login, card, text secret or file, so the value never passes through chat or a model. Prefill what you know: the site and username of a login, a card’s name, the variable name of a secret or file. Send the returned url to the person (as a button with cta in a chat) and stop: it opens the request in their Settings → Secrets, signed in, where it waits until they save or dismiss it. It never expires, and asking again for the same thing returns the same request. Saving it wakes this chat, or continues this Task from a Run.
update
update
Rename a Vault item or change who can use it. Its owner or a company admin can change it.OAuth-only.
Output
Secret metadata, a human entry request, or the update/deletion result. Listing metadata does not reveal secret values. The result uses MCPcontent 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.