Read AgendaPro bookings, slots, clients, services and sales; create, update and cancel bookings. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"agendapro": {
"url": "https://agendapro.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"agendapro": {
"type": "http",
"url": "https://agendapro.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your AgendaPro API key.
API access needs the Pro plan. Create the key in AgendaPro → Configuraciones → Integraciones (it is shown only once, and a company can have 2 active keys, so a dedicated key for this connection is easy to revoke). A key limited to some scopes limits the tools in the same way, and it needs at least one of the scopes locations:read, providers:read or services:read (they identify your company). Your key is used only to call the AgendaPro API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your AgendaPro API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the AgendaPro connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
agendapro_list_locations | read | 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. |
agendapro_get_location | read | Get location One location by id, with address, coordinates, timezone and weekly opening hours. GET /v3/locations/{id}. |
agendapro_list_services | read | 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. |
agendapro_get_service | read | Get service One service by id, including its category, images and the providers who perform it. GET /v3/services/{id}. |
agendapro_list_service_categories | read | List service categories List service categories, ordered as the business arranges them. GET /v3/categories. |
agendapro_list_providers | read | 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. |
agendapro_get_provider | read | Get provider One service provider by id, with biography, images and working hours including breaks. GET /v3/providers/{id}. |
agendapro_list_bookings | read | 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. |
agendapro_get_booking | read | Get booking One booking by id with status, service, provider, client id, location, prices, notes and the linked sale. GET /v3/bookings/{id}. |
agendapro_list_available_slots | read | 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. |
agendapro_create_booking | write | 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. |
agendapro_update_booking | write | 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}. |
agendapro_cancel_booking | write | 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. |
agendapro_list_clients | read | 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. |
agendapro_search_clients | read | 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. |
agendapro_get_client | read | Get client One client by id with contact details, address, birth date, record number and active flag. GET /v3/clients/{id}. |
agendapro_list_client_custom_attributes | read | List a client's custom attributes The custom attribute values stored for one client (id, name, datatype, value). GET /v3/clients/{id}/custom_attributes. |
agendapro_list_custom_attributes | read | 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 | write | 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. |
agendapro_update_client | write | Update client WRITE: change an existing client (partial update: only the fields you pass change; it overwrites the stored value). PATCH /v3/clients/{id}. |
agendapro_list_sales | read | 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. |
agendapro_get_sale | read | Get sale One sale by id with amounts, status, location and its payment transactions (amount, paid-at, payment method). GET /v3/sales/{id}. |
agendapro_list_products | read | List products List retail products in the catalog: name, SKU, price, active flag, category, brand and display. GET /v3/products. |
agendapro_get_product | read | Get product One catalog product by id with description, SKU, price, category, brand and display. GET /v3/products/{id}. |
agendapro_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
agendapro_request_feature | Request a missing feature Tell usefulapi that the user needs something the AgendaPro tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
agendapro_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on AgendaPro (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. Returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
agendapro_cancel_subscription | Cancel the Pro subscription Cancel the caller's AgendaPro Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run agendapro_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this AgendaPro server only. Subscribe with agendapro_upgrade (it returns a Stripe Checkout link). Cancel any time with agendapro_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running agendapro_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by AgendaPro. The server calls the AgendaPro API with your own AgendaPro access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your AgendaPro API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your AgendaPro API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the AgendaPro API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in AgendaPro.
Yes, if you approve it. 5 of the 24 AgendaPro tools can create or change data. The other 19 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this AgendaPro server only. Cancel any time: Pro then runs to the end of the paid period. Run agendapro_usage_status to see how many calls you used.
Ask the AI to run agendapro_upgrade: it returns a Stripe Checkout link. To cancel, run agendapro_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with agendapro_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.