Partelisto

Guest check-in, SES.HOSPEDAJES status, and booking creation for Spanish vacation rentals. No PII.

Should I use this

Quality & Safety

A
Description quality
96%
Schema completeness
87%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'get_usage_summary' description lacks action verbin get_usage_summary

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,155Tokens (tool definitions)
~790 BTypical response size
Moderate attention impact (0.90% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "partelisto-mcp": {
      "url": "https://mcp.partelisto.es/mcp"
    }
  }
}

Remote endpoints

https://mcp.partelisto.es/mcpstreamable-http

What it can do

Tool inventory

Tools (8)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟡create_booking(propertyId, checkIn, checkOut, templateId, guestName, ...)

Creates a new booking (a check-in workflow) for one of the host's properties. Requires the write permission granted separately during sign-in. Ask the host to confirm the property and dates before calling this. Does not email the guest — call send_guest_checkin_link afterwards if a link should go out now.

Input Schema

{
  "type": "object",
  "properties": {
    "propertyId": {
      "description": "The property id, from list_properties.",
      "type": "string"
    },
    "checkIn": {
      "description": "Check-in date, yyyy-MM-dd.",
      "type": "string"
    },
    "checkOut": {
      "description": "Check-out date, yyyy-MM-dd.",
      "type": "string"
    },
    "templateId": {
      "description": "Check-in template id. Omit if the property has exactly one active (non-archived) template — it is picked automatically; otherwise this is required.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    },
    "guestName": {
      "description": "Guest name, optional.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    },
    "guestEmail": {
      "description": "Guest email, optional.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    },
    "guestPhone": {
      "description": "Guest phone, optional.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    }
  },
  "required": [
    "propertyId",
    "checkIn",
    "checkOut"
  ]
}
🟡send_guest_checkin_link(bookingId, email, guestName)

Sends (or resends) the guest check-in link by email for a booking the host owns. This is a real action with a side effect: it emails the guest and, on resend, invalidates the guest's previous link. Requires the write permission granted separately during sign-in. Ask the host to confirm before calling this.

Input Schema

{
  "type": "object",
  "properties": {
    "bookingId": {
      "description": "The booking id.",
      "type": "string"
    },
    "email": {
      "description": "Guest email to send to. Omit to use the email already on the booking.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    },
    "guestName": {
      "description": "Guest name, for the email greeting. Omit to keep the name already on the booking.",
      "type": [
        "string",
        "null"
      ],
      "default": null
    }
  },
  "required": [
    "bookingId"
  ]
}
🟢list_ses_statuses(bookingIds)

SES.HOSPEDAJES (police registration) submission status for a set of bookings the host owns: status, attempts, last error, and the official reference once accepted. Bookings with no submission yet are omitted.

Input Schema

{
  "type": "object",
  "properties": {
    "bookingIds": {
      "description": "Booking ids to check, up to 50.",
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "bookingIds"
  ]
}
🟢get_guest_form_status(bookingId)

Whether the guest has completed the check-in form for a booking the host owns (None or Submitted). No form content.

Input Schema

{
  "type": "object",
  "properties": {
    "bookingId": {
      "description": "The booking id.",
      "type": "string"
    }
  },
  "required": [
    "bookingId"
  ]
}
🟢list_bookings(skip, take)

Lists the signed-in host's bookings (newest first), paged. Returns id, property id, check-in/check-out dates, status, and whether a check-in link and guest contact exist — never the guest's email, phone, or documents.

Input Schema

{
  "type": "object",
  "properties": {
    "skip": {
      "description": "Rows to skip, for paging. Defaults to 0.",
      "type": "integer",
      "default": 0
    },
    "take": {
      "description": "Rows to return, max 50. Defaults to 20.",
      "type": "integer",
      "default": 20
    }
  }
}
🟢get_attention_required(arrivalWindowDays)

Scans the signed-in host's most recent bookings (up to 50) and returns only what needs action right now: stays that are imminent or under way where the guest has not completed check-in, and bookings whose SES.HOSPEDAJES submission failed. Empty list means nothing needs attention within the window. No guest PII.

Input Schema

{
  "type": "object",
  "properties": {
    "arrivalWindowDays": {
      "description": "How many days ahead counts as \"imminent\" (a negative gap means the stay already started). Defaults to 3.",
      "type": "integer",
      "default": 3
    }
  }
}
🟢list_properties(includeArchived)

Lists the signed-in host's properties: id, name, address, municipality/province, and whether it is archived. No guest data.

Input Schema

{
  "type": "object",
  "properties": {
    "includeArchived": {
      "description": "Include archived properties. Defaults to false.",
      "type": "boolean",
      "default": false
    }
  }
}
🟢get_usage_summary

The signed-in host's plan tier, trial status, and this month's usage against plan limits (properties, templates, bookings).

Input Schema

{
  "type": "object",
  "properties": {}
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded8 tools
verifiedversion not recorded8 tools
verifiedversion not recorded8 tools