> ## Documentation Index
> Fetch the complete documentation index at: https://docs.melso.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Melso product MCP: https://melso.ai/api/mcp (OAuth; one company per grant). REST: https://melso.ai. Documentation-search MCP: https://docs.melso.ai/mcp. The docs search server does not act on customer accounts.
>
> Use the live tool schema and respect company membership. Ask the person to authorize the exact fiscal document version in the signed-in app. A professional prepares and files included returns after authorization; AI does not file alone. A prepared file or approval receipt is not evidence of filing. Never claim completion from an accepted Task or Run. Keep credentials out of chat and logs. Agents features are internal or by private invitation.

# request_approval

> Input, output and examples for the request_approval MCP tool.

<Info>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](/essentials/quickstart).</Info>

Ask the human to approve or reject a specific proposed action on this Task. Parks until they decide. The tool result names that exact payload, not a generic approved flag.

**Availability:** Managed Runs only; external OAuth excluded.

**Catalog:** Core (`tools/list`).

<Info>Available to managed Runs. External OAuth connections do not list this tool.</Info>

The live catalog is authoritative: company type, membership, plan, connected apps and execution context can narrow this contract. [Understand access](/mcp/permissions).

## Input

### Agents / Autónomo / Company schema

```json theme={null}
{
  "properties": {
    "action": {
      "description": "Exact proposed action this approval binds to.",
      "type": "string"
    },
    "message": {
      "description": "What the human must approve or reject.",
      "type": "string"
    },
    "task_id": {
      "description": "Task UUID or identifier. Defaults to the current Run's Task.",
      "type": "string"
    },
    "title": {
      "description": "Optional card title.",
      "type": "string"
    }
  },
  "required": [
    "message"
  ],
  "type": "object"
}
```

## Output

A pending approval interaction attached to the Run. The returned request does not grant permission to perform the proposed action.

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. The server does not currently declare an `outputSchema`, so treat additional fields as extensible. [Result handling](/mcp/results).

## Example

Use a Run token for this managed-context example. External OAuth clients cannot call this tool. Replace example identifiers with values from your own Task. Write actions change data.

```bash theme={null}
curl --fail-with-body https://melso.ai/api/mcp \
  -H "Authorization: Bearer $MELSO_MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  --data-binary @- <<'JSON'
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "request_approval",
    "arguments": {
      "message": "Example message"
    }
  }
}
JSON
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.