# AgendaPro MCP by usefulapi (remote · agendapro.usefulapi.io)

Read AgendaPro bookings, slots, clients, services and sales; create, update and cancel bookings.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `agendapro.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-agendapro/agendapro.md), [page](https://verifymcp.io/servers/io-usefulapi-agendapro/agendapro)

## Channel facts

- Endpoint: `https://agendapro.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3430 tokens (~142/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the AgendaPro MCP by usefulapi server?

AgendaPro MCP by usefulapi is a hosted endpoint at https://agendapro.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-agendapro 'https://agendapro.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-agendapro": {
      "url": "https://agendapro.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-agendapro": {
      "type": "http",
      "url": "https://agendapro.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-agendapro]
url = "https://agendapro.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-agendapro": {
      "type": "remote",
      "url": "https://agendapro.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-agendapro --url 'https://agendapro.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-agendapro:
    url: "https://agendapro.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-agendapro": {
      "Transport": "http",
      "Url": "https://agendapro.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-agendapro -t streamable-http -u 'https://agendapro.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-agendapro": {
      "type": "http",
      "url": "https://agendapro.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.2.1 → 1.2.3
- [functional] Server version: 1.2.0 → 1.2.1

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (24)

### `agendapro_list_locations` (~124 tokens)

List locations

List the business's locations (sucursales / locales): id, name, address, phone, email, timezone, opening hours and country. Location ids are needed for bookings, slots and sales filters. GET /v3/locations.

Input parameters:

- `active` (boolean): Only active (true) or inactive (false) locations.
- `page` (integer): Page number, from 1 (default 1). Pass pagination.next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 30).

### `agendapro_get_location` (~48 tokens)

Get location

One location by id, with address, coordinates, timezone and weekly opening hours. GET /v3/locations/{id}.

Input parameters:

- `location_id` (integer, required): AgendaPro location id.

### `agendapro_list_services` (~122 tokens)

List services

List the services (treatments, classes, sessions) the business offers: id, name, price, duration, type, category, whether online booking/payment is on, and the location. Service ids are needed to book. GET /v3/services.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass pagination.next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 30).
- `provider_id` (integer): Only services this provider performs.

### `agendapro_get_service` (~48 tokens)

Get service

One service by id, including its category, images and the providers who perform it. GET /v3/services/{id}.

Input parameters:

- `service_id` (integer, required): AgendaPro service id.

### `agendapro_list_service_categories` (~76 tokens)

List service categories

List service categories, ordered as the business arranges them. GET /v3/categories.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass pagination.next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 30).

### `agendapro_list_providers` (~188 tokens)

List providers

List service providers (the staff who take bookings): id, public name, location, active flag, online-booking flag and working hours. Provider ids are needed to book. GET /v3/providers.

Input parameters:

- `active` (boolean): Only active (true) or inactive (false) providers.
- `location_ids` (array): Only providers at these locations.
- `order_by` (string): Sort direction.
- `page` (integer): Page number, from 1 (default 1). Pass pagination.next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 30).
- `public_name` (string): Partial match on the provider's public name.
- `service_ids` (array): Only providers who perform these services.
- `sort_by` (string): Field to sort by, e.g. public_name.

### `agendapro_get_provider` (~47 tokens)

Get provider

One service provider by id, with biography, images and working hours including breaks. GET /v3/providers/{id}.

Input parameters:

- `provider_id` (integer, required): AgendaPro provider id.

### `agendapro_list_bookings` (~258 tokens)

List bookings

List bookings (reservas / appointments) with time, status, service, provider, client id, location, price and the linked sale. AgendaPro requires at least ONE of client_id, location_id, service_id or service_provider_id; dates only narrow the result. A sale may be a membership covering several bookings, so do not total amounts by sale id. GET /v3/bookings.

Input parameters:

- `client_id` (integer): Bookings of this client.
- `end_date` (string): Bookings until this date, yyyy-mm-dd.
- `location_id` (integer): Bookings at this location.
- `page` (integer): Page number, from 1 (default 1). Pass pagination.next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 30).
- `scheduled` (boolean): Filter by the scheduled flag.
- `service_id` (integer): Bookings of this service.
- `service_provider_id` (integer): Bookings of this provider.
- `start_date` (string): Bookings from this date, yyyy-mm-dd.
- `status_id` (integer): Filter by booking status id (see the status object on a booking).

### `agendapro_get_booking` (~56 tokens)

Get booking

One booking by id with status, service, provider, client id, location, prices, notes and the linked sale. GET /v3/bookings/{id}.

Input parameters:

- `booking_id` (integer, required): AgendaPro booking id.

### `agendapro_list_available_slots` (~116 tokens)

List available slots

Free booking time windows at a location on one date (optionally for one service and/or provider): start/end time, provider, plus a metadata summary (service duration, slot count). Use before creating a booking. GET /v3/available_slots.

Input parameters:

- `location_id` (integer, required): Location to check.
- `provider_id` (integer): Only slots of this provider.
- `service_id` (integer): Only slots for this service.
- `start_date` (string, required): The date to check, yyyy-mm-dd.

### `agendapro_create_booking` (~272 tokens)

Create booking

WRITE: create a booking for an existing client, service, provider and location. Check agendapro_list_available_slots first. status_id must be a non-cancelled status: copy the status.id of an existing booking (agendapro_list_bookings). AgendaPro does NOT send email/SMS/WhatsApp notifications for bookings created through the API. Not idempotent: calling twice books twice. POST /v3/bookings.

Input parameters:

- `client_id` (integer, required): Client id (agendapro_search_clients / agendapro_create_client).
- `end_time` (string): End; defaults to start + the service duration.
- `location_id` (integer, required): Location id.
- `notes`: Booking notes.
- `price` (string): Price as a decimal string; defaults to the service price.
- `provider_id` (integer, required): Service provider id.
- `service_id` (integer, required): Service id.
- `start_time` (string, required): Start, ISO 8601 with a timezone offset, e.g. 2026-03-10T10:00:00-03:00 (use the location's timezone).
- `status_id` (integer, required): A non-cancelled booking status id.
- `time_resource_id`: Time resource id; required when the service needs one.

### `agendapro_update_booking` (~226 tokens)

Update booking

WRITE: change an existing booking (partial update: only the fields you pass change): move it, switch service/provider/location, change status, price or notes. The merchant's customer policy applies: a change too close to the start time, or past the maximum number of changes, is refused with HTTP 422 and must not be retried. PATCH /v3/bookings/{id}.

Input parameters:

- `booking_id` (integer, required): AgendaPro booking id.
- `client_id` (integer)
- `end_time` (string): New end, ISO 8601 with a timezone offset.
- `location_id` (integer)
- `notes`: New notes; null clears them.
- `price` (string)
- `provider_id` (integer)
- `service_id` (integer)
- `start_time` (string): New start, ISO 8601 with a timezone offset.
- `status_id` (integer): New booking status id (copy from another booking's status.id).
- `time_resource_id`: New time resource id; null removes the assigned resource.

### `agendapro_cancel_booking` (~104 tokens)

Cancel booking

WRITE: cancel a booking. This cannot be undone through the API. The merchant's customer policy applies: a cancellation that is disabled, too close to the start time or past the maximum number of changes is refused with HTTP 422 (tell the user the merchant does not allow it; do not retry). Confirm with the user before calling. PATCH /v3/bookings/{id}/cancel.

Input parameters:

- `booking_id` (integer, required): AgendaPro booking id to cancel.

### `agendapro_list_clients` (~119 tokens)

List clients

List the business's clients (customers) page by page: name, email, phone, identification number, address, birth date, record number, active flag. Personal data: only use it for the task at hand. To find one person use agendapro_search_clients. GET /v3/clients.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass pagination.next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 30).

### `agendapro_search_clients` (~94 tokens)

Search clients

Find clients by free text (name, email, phone, identification number or record number): a short ranked list with id, full name, email, phone. The fastest way to get a client_id. GET /v3/clients/quick-search.

Input parameters:

- `limit` (integer): Max results, 1-25 (default 10).
- `q` (string, required): Search text, max 50 characters.

### `agendapro_get_client` (~51 tokens)

Get client

One client by id with contact details, address, birth date, record number and active flag. GET /v3/clients/{id}.

Input parameters:

- `client_id` (integer, required): AgendaPro client id.

### `agendapro_list_client_custom_attributes` (~54 tokens)

List a client's custom attributes

The custom attribute values stored for one client (id, name, datatype, value). GET /v3/clients/{id}/custom_attributes.

Input parameters:

- `client_id` (integer, required): AgendaPro client id.

### `agendapro_list_custom_attributes` (~51 tokens)

List custom attribute templates

The custom client fields the business defined (id, name, datatype, mandatory, group, choices). Use the template ids when setting custom_attributes on a client. GET /v3/custom_attributes.

### `agendapro_create_client` (~336 tokens)

Create client

WRITE: create a new client. first_name is required and at least one of last_name, email or phone must also be given (AgendaPro's rule). Search first (agendapro_search_clients) to avoid duplicates; not idempotent. No message is sent to the client. POST /v3/clients.

Input parameters:

- `address` (string): Street address. On update, an empty string clears the stored value.
- `age` (integer): Age in years.
- `birth_day` (integer): Day of birth, 1-31.
- `birth_month` (integer): Month of birth, 1-12.
- `birth_year` (integer): Year of birth.
- `city` (string): City. On update, an empty string clears the stored value.
- `custom_attributes` (array): Custom attribute values to set.
- `district` (string): District or neighborhood. On update, an empty string clears the stored value.
- `email` (string): Email (stored lowercase).
- `first_name` (string, required): First name.
- `gender`: 0 = other, 1 = female, 2 = male.
- `identification_number` (string): National identification number (RUT, DNI, CURP...). On update, an empty string clears the stored value.
- `last_name` (string): Last name. On update, an empty string clears the stored value.
- `phone` (string): Phone in E.164 format, e.g. +56912345678.
- `region` (string): Region or state. On update, an empty string clears the stored value.

### `agendapro_update_client` (~316 tokens)

Update client

WRITE: change an existing client (partial update: only the fields you pass change; it overwrites the stored value). PATCH /v3/clients/{id}.

Input parameters:

- `address` (string): Street address. On update, an empty string clears the stored value.
- `age` (integer): Age in years.
- `birth_day` (integer): Day of birth, 1-31.
- `birth_month` (integer): Month of birth, 1-12.
- `birth_year` (integer): Year of birth.
- `city` (string): City. On update, an empty string clears the stored value.
- `client_id` (integer, required): AgendaPro client id.
- `custom_attributes` (array): Custom attribute values to set.
- `district` (string): District or neighborhood. On update, an empty string clears the stored value.
- `email` (string): Email (stored lowercase).
- `first_name` (string): First name.
- `gender`: 0 = other, 1 = female, 2 = male.
- `identification_number` (string): National identification number (RUT, DNI, CURP...). On update, an empty string clears the stored value.
- `last_name` (string): Last name. On update, an empty string clears the stored value.
- `phone` (string): Phone in E.164 format, e.g. +56912345678.
- `region` (string): Region or state. On update, an empty string clears the stored value.

### `agendapro_list_sales` (~173 tokens)

List sales

List sales (ventas): status (partially_paid, paid, canceled, refunded), paid and pending amounts, paid-at time, location, client id and the payment transactions. Filter by paid date range, location or client. GET /v3/sales.

Input parameters:

- `client_id` (integer): Sales to this client.
- `location_id` (integer): Sales at this location.
- `page` (integer): Page number, from 1 (default 1). Pass pagination.next_page from the previous reply.
- `paid_at_end` (string): Sales paid until this date (inclusive), yyyy-mm-dd.
- `paid_at_start` (string): Sales paid from this date (inclusive), yyyy-mm-dd.
- `per_page` (integer): Results per page, 1-100 (default 30).

### `agendapro_get_sale` (~55 tokens)

Get sale

One sale by id with amounts, status, location and its payment transactions (amount, paid-at, payment method). GET /v3/sales/{id}.

Input parameters:

- `sale_id` (integer, required): AgendaPro sale id.

### `agendapro_list_products` (~168 tokens)

List products

List retail products in the catalog: name, SKU, price, active flag, category, brand and display. GET /v3/products.

Input parameters:

- `active` (boolean): Only active (true) or inactive (false) products.
- `page` (integer): Page number, from 1 (default 1). Pass pagination.next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 30).
- `product_brand_id` (string): Brand id, or 'none'.
- `product_category_id` (string): Category id, or 'none' for products without a category.
- `product_display_id` (string): Display id, or 'none'.
- `search` (string): Free text over product name and SKU.

### `agendapro_get_product` (~49 tokens)

Get product

One catalog product by id with description, SKU, price, category, brand and display. GET /v3/products/{id}.

Input parameters:

- `product_id` (integer, required): AgendaPro product id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-agendapro/agendapro#diagnostics

## Score history

- 2026-10-25: 62
- 2026-10-24: 62

## Common questions

### What is the AgendaPro MCP by usefulapi server?

AgendaPro MCP by usefulapi is listed in the public MCP registry as io.usefulapi/agendapro. Read AgendaPro bookings, slots, clients, services and sales; create, update and cancel bookings. This page covers its hosted endpoint (https://agendapro.usefulapi.io/mcp).

### Is the AgendaPro MCP by usefulapi server safe to use?

AgendaPro MCP by usefulapi scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the AgendaPro MCP by usefulapi server expose?

AgendaPro MCP by usefulapi exposes 24 tools: agendapro_list_locations, agendapro_get_location, agendapro_list_services, agendapro_get_service, agendapro_list_service_categories, and 19 more. Their descriptions and schemas cost roughly 3,151 tokens of context every time the server is loaded.

### Does the AgendaPro MCP by usefulapi server require authentication?

Yes. AgendaPro MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the AgendaPro MCP by usefulapi server still maintained?

AgendaPro MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agendapro.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/agendapro/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-agendapro/agendapro.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-agendapro/agendapro.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-agendapro/agendapro