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.
An OAuth connection acts for one person in the company selected at consent. The server checks current membership and resource access on every call. Passing another workspace_id to a tool cannot switch that binding.

​
The catalog follows the account

Autónomo companies expose the supported fiscal workflow. Agents companies expose technical controls only where access has been granted. Plans and service availability can reduce fiscal writes to read-only access. An isolated Task’s Run has a smaller tool allowlist. tasks_watch, ask_user, and request_approval serve managed Run or conversation contexts. External OAuth clients do not receive these tools. They can inspect pending Task interactions through the tools their connection does expose.

​
Preparation is not authorization

No customer MCP tool approves, files or pays.
  • An invoice tool can prepare a draft and return a web approval link. Only the person can approve issuance there.
  • A tax tool can prepare a preview or an import file. That is not a submission to the tax authority.
  • Payment recording records money already received; it does not move money.
  • Fiscal authorization applies to the exact saved version. A changed version needs fresh authorization in the app.
A professional prepares and files the included returns after authorization. Check the approval and filing guide for what counts as evidence of filing.

​
Keep secrets in their own flow

Use a returned secure entry or connection link when a service needs credentials. Do not ask the person to paste secret values into a conversation, a Task or a support ticket.