> ## 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.

# tasks_send

> Input, output and examples for the tasks_send 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>

Add a message with new instructions to a Task. It starts a Run when the Task is idle, or queues behind the active Run. A Task without execution settings and no prior Run saves the message only; then use tasks\_control start. It does not answer a pending question card: the card is cancelled as superseded. To answer it, use tasks\_control answer.

**Availability:** Autónomo / Empresa / Agents invitation.

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

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 / Managed run / agents / Managed run / company / Managed run / freelancer schema

```json theme={null}
{
  "additionalProperties": false,
  "properties": {
    "attachment_ids": {
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "content": {
      "description": "Follow-up instructions.",
      "type": "string"
    },
    "id": {
      "description": "Task UUID or identifier, such as MELS-818.",
      "type": "string"
    }
  },
  "required": [
    "id",
    "content"
  ],
  "type": "object"
}
```

## Output

A message receipt containing `message_id` and `queued`, plus `run_id` and `attachment_ids` when present. A saved message may have no Run ID.

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 an OAuth access token issued for this MCP resource (a Run token for Run-only tools). Replace example identifiers with values from your own account. 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": "tasks_send",
    "arguments": {
      "content": "Example content",
      "id": "11111111-1111-4111-8111-111111111111"
    }
  }
}
JSON
```


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