> ## 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 MCP: https://mcp.melso.ai/mcp (OAuth; one company per connection). Documentation-search MCP: https://docs.melso.ai/mcp; it does not act on customer accounts. Melso API: https://api.melso.ai/v1, invoicing only, with a company API key.
>
> Use the live tool list and respect company membership. Ask the person to approve the exact invoice or tax return version in the signed-in app. Melso's professionals prepare and file included returns after approval; an AI assistant does not file. A prepared file or an approval is not evidence of filing: only the AEAT's reference and receipt are. Keep credentials out of chat and logs.

# Qué incluye cada plan — plans MCP

> MCP plans: what each Melso plan includes, what is paid apart and what Melso does not do, for this company.

What each Melso plan includes, what is paid apart and what Melso does not do, for this company. Read it before telling the person what Melso covers or costs, and before filing a ticket that asks it.

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

The live tool list is authoritative: the company's plan and your role can narrow this contract. [Understand access](https://docs.melso.ai/mcp/permissions.md).

## When to use

Read it before you tell the person what Melso covers or costs, and before you file a ticket that asks it: what each plan includes, what is paid apart (such as modelo 720 or a digital certificate Melso obtains) and what Melso does not do. Answer from these facts only. When they do not say, file `support_tickets_create` with the person's question instead of guessing.

## Input

```json theme={null}
{
  "additionalProperties": false,
  "properties": {},
  "type": "object"
}
```

## Output

A JSON object with `facts`: each one a `topic` and a `fact` in Spanish, in the customer's words, about what a plan includes, what is paid apart or what Melso does not do, for this company's kind. Prices appear as Billing charges them. It changes nothing.

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. When the server declares an `outputSchema`, it is reproduced below. Check the action result and its declared fields before reporting success.

### Declared output schema

```json theme={null}
{
  "properties": {
    "facts": {
      "items": {
        "properties": {
          "fact": {
            "type": "string"
          },
          "topic": {
            "type": "string"
          }
        },
        "required": [
          "topic",
          "fact"
        ],
        "type": "object"
      },
      "type": "array"
    }
  },
  "required": [
    "facts"
  ],
  "type": "object"
}
```

## Example

Answer whether Melso includes something before you file a ticket about it. These are the `arguments` of each call, in order.

**1. Read what Melso includes for this company**

```json theme={null}
{}
```

The first call as a request. Use an OAuth access token issued for this MCP resource and replace the example identifiers with values from your own company.

```bash theme={null}
curl --fail-with-body https://mcp.melso.ai/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": "plans",
    "arguments": {}
  }
}
JSON
```


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