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

# support_tickets_create

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

File a bug, feature request, or question into Melso's own Support backlog for the team to triage. Always available, to every member and every agent, regardless of workspace or Area — use it whenever you hit a bug, a missing capability, or have a question about the Melso platform itself, and whenever a person asks for something Melso cannot do on its own (type service\_request). The ticket is created idle: it starts no Run and nobody works it automatically. When you suspect this was already reported, search with support\_tickets\_list (found with tools\_search) first: the same title from you within the last 24h returns the existing ticket instead of filing a new one.

**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 schema

```json theme={null}
{
  "additionalProperties": false,
  "properties": {
    "attachment_ids": {
      "description": "Attachment UUIDs from multipart POST to this MCP URL plus /upload-file. Recorded as references in the ticket body only — not re-uploaded into the Support backlog.",
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "client_request_id": {
      "description": "Caller-generated UUID for safe create retries. Reuse it after an uncertain response.",
      "type": "string"
    },
    "description": {
      "description": "What happened (bug), what's wanted (feature_request), or the question — with enough detail for triage to act on.",
      "type": "string"
    },
    "severity": {
      "description": "blocking: cannot proceed. degraded: a workaround exists. nice_to_have: no urgency. Defaults to nice_to_have.",
      "enum": [
        "blocking",
        "degraded",
        "nice_to_have"
      ],
      "type": "string"
    },
    "source_task_id": {
      "description": "The Task you were working when you hit this, e.g. MELS-123.",
      "type": "string"
    },
    "title": {
      "description": "One-line ticket title, e.g. \"tasks_create rejects a valid area_id\". No newlines.",
      "type": "string"
    },
    "type": {
      "description": "bug: something is broken. feature_request: a capability is missing. question: unclear behavior worth asking about. service_request: something a person asked for that Melso cannot do on its own, which Melso people must do (a registration, a filing, a change to submitted details); put every detail they gave in the description.",
      "enum": [
        "bug",
        "feature_request",
        "question",
        "service_request"
      ],
      "type": "string"
    }
  },
  "required": [
    "title",
    "type"
  ],
  "type": "object"
}
```

## Output

The saved support ticket receipt. A ticket’s creation is not confirmation that the reported issue has been resolved.

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": "support_tickets_create",
    "arguments": {
      "description": "A document is missing from my account.",
      "title": "Example title",
      "type": "bug"
    }
  }
}
JSON
```


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