Setmore MCP server for your AI

Setmore issues it per account, and API access is only available on a paid Setmore Pro plan. If you don't have a token yet, email api@setmore.com from the address your Setmore account is registered under and ask for API access. Paste the value Setmore sends back into the Refresh token field on the connect form.

No. The connect form asks for a Refresh token plus an optional Connection type label, and that is the whole setup — no redirect URL, no client secret, and never your Setmore password. PopMCP exchanges the refresh token server-side for a short-lived access token and renews it automatically, so there is nothing to re-paste later.

Canceling maps to delete_appointment, which attempts to delete an appointment by its key. There is no operation that moves an existing booking's start or end time, so a reschedule is really a cancel followed by a fresh create_appointment. update_appointment_label changes only the appointment's label — its status text — not when it happens.

search_customers looks people up by first name, email and/or phone, all passed as query params, and create_customer adds anyone who isn't already on file. Those are the only two customer operations, so the connection cannot edit or delete a customer record. In practice the agent searches first, creates only on a miss, then books.

Eleven, spread across five API modules: Appointments, Services, Customers, Slots and Staff. Seven are reads and four are writes; ten load into your AI client by default and the remaining one is searchable, so you can pull it in on demand. PopMCP also absorbs Setmore's path inconsistencies — booking uses the singular appointment/create while the list is plural, and staff live at staffs — so you never have to think about them.

Change detection covers appointments being booked, rescheduled, canceled or relabeled — confirmed, no-show and so on — plus services being added or having their price or duration edited, and staff joining or leaving the booking calendar. There is also a threshold watch, Day fully booked, which fires when open slots for a staff member and service drop to none for a day. Note the rescheduled watch spots time changes made inside Setmore, even though no operation performs one.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Connect Setmore in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Setmore on the consent screen. The Setmore tools are then available in that session, and no Setmore credential is stored on your machine.

Loading 11 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 10-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.

A tool is something your AI calls, and there are 11 here. A trigger is something PopMCP watches for you: 9 Setmore events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Setmore.