# Boulevard MCP connector

The Boulevard connector brings appointments, bookings, arrivals, ratings and account credits into Claude, ChatGPT, Cursor and Microsoft Copilot, so each person books, reschedules and updates Boulevard under their own sign-in with every change logged.

Source: https://elaichi.ai/connectors/boulevard/

## Facts

| | |
| --- | --- |
| Application | Boulevard |
| Category | CRM |
| AI tools | 196 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Boulevard is connected

- Which appointments are booked for tomorrow afternoon?
- Find open times to move Dana's Friday blowout to next week.
- Show me this week's appointment ratings below four stars.

## Connect Boulevard in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Boulevard.
2. Optionally set Share with, then press Connect.
3. Supply your own Boulevard app, then approve. Boulevard needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Boulevard tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Boulevard MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Boulevard MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Boulevard MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Boulevard MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Boulevard MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Boulevard to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Boulevard tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Boulevard through Elaichi

### Book the appointment during the call

Front desk. Ask which times are open, book the service for the client, add an addon and leave a note on the booking while they are still on the phone.

### Reschedule without the back and forth

Front desk. Ask for the open dates and times for a client's appointment, pick one, and move it in Boulevard in a single exchange.

### Pull up the day's appointments at a glance

Operations. List today's appointments by location, check who is booked with whom, and mark clients as arrived as they walk in.

### Read every appointment rating in one place

Management. Pull the latest appointment ratings from Boulevard and ask which providers and services are drawing the lowest scores this month.

### Adjust account credit after a bad visit

Finance. When a visit goes wrong, add an account credit adjustment to the client's Boulevard account and record why it was given.

### Move a service to another provider

Service providers. Reassign a booked service to a different staff member, change its duration or price, and attach the right room or chair in Boulevard.

## Elaichi vs Zapier MCP vs Composio for Boulevard

All three can connect Boulevard to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Boulevard tools | Allow or restrict single Boulevard tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Boulevard call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Boulevard to Claude?

Connecting Boulevard to Claude takes two steps. First, connect Boulevard in Elaichi: Boulevard requires an OAuth application registered inside your own Boulevard account, so somebody brings that client ID and secret into Elaichi once, then each person signs in to Boulevard as themselves. Second, in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Boulevard then shows up in Claude under your own sign-in.

### Does Boulevard work with ChatGPT and Cursor as well as Claude?

Yes. Once Boulevard is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Boulevard once and every client sees it.

### What can an AI agent actually do with my Boulevard data?

With Boulevard connected, an agent can list and look up appointments, book new ones, find open dates and times and reschedule, cancel, mark a client as arrived, update notes, services, staff, duration and price on a booking, read appointment ratings, and add account credit adjustments. Short, concrete asks work best, such as which afternoon slots are open for a 60 minute color on Thursday. Long multi-part instructions tend to get muddled.

### Does connecting Boulevard give the AI access to every location and client?

No. Every call into Boulevard runs as the person who signed in, so an agent sees only the locations, appointments and clients that person can already see in Boulevard. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Boulevard itself allows that person.

### Can my team share one Boulevard connection?

Yes. One person connects Boulevard in Elaichi and shares the connection with a team, and nobody else ever handles the client ID, secret or any other credential. Each teammate still signs in as themselves, so the audit log names the actual person who booked, rescheduled or cancelled a Boulevard appointment.

### Can I stop an agent from deleting or changing things in Boulevard?

Yes. Restrictions in Elaichi are set per action, for example cancelling a Boulevard appointment or changing a service price, and they apply to a role or to one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Boulevard connection when someone leaves?

Offboarding a person in Elaichi ends their access to Boulevard at once, across every client they used. A shared Boulevard connection keeps working for everyone else on the team. If you want Boulevard gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

### Does the Boulevard MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Boulevard is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Boulevard?

Yes. Both let Claude, ChatGPT or Cursor use Boulevard. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Boulevard call.

### How is Elaichi different from Composio for Boulevard?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Boulevard: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 196 Boulevard tools

Every tool below is callable through https://api.elaichi.ai/mcp once Boulevard is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Boulevard account credit adjustment** (Create). Adjust the account credit balance for a client. GraphQL mutation createAccountCreditAdjustment. Scope: client:write. Required: balanceDelta, locationId, staffId, client_id.
- **Boulevard app uninstalls confirm** (Action). Ack uninstall app. GraphQL mutation ackUninstallApp.
- **Create a Boulevard appointment booking** (Create). Create a booking from an existing appointment. GraphQL mutation bookingCreateFromAppointment. Scope: appointment:write. Required: appointmentId.
- **List all Boulevard appointment ratings** (List). Appointment ratings. GraphQL query appointmentRatings. Scope: appointment:read. The connector pages through all results (first / after; limit sets first, default 100).
- **Boulevard appointments cancel** (Cancel). Cancel an Appointment. Cancelling an Appointment automatically updates its state to cancelled. GraphQL mutation cancelAppointment. Scope: appointment:write. Required: reason, appointment_id.
- **Get single Boulevard appointment by ID** (Get). Look up an appointment by ID. GraphQL query appointment. Scope: appointment:read. Required: id.
- **List all Boulevard appointments** (List). List appointments for a location The appointment connection supports queries on the following fields: * id: Id * startAt: DateTime * createdAt: DateTime * cancelled: Boolean * staffId: Id. GraphQL query appointments. Scope: appointment:read. Required: locationId. The connector pages through all results (first / after; limit sets first, default 100).
- **Boulevard appointments lookup reschedule dates** (Action). Get the available dates for the provided appointment. GraphQL mutation appointmentRescheduleAvailableDates. Scope: appointment:read. Required: appointmentId, searchRangeLower, searchRangeUpper.
- **Boulevard appointments lookup reschedule times** (Action). Get the available appointment times on a particular date for the provided appointment. GraphQL mutation appointmentRescheduleAvailableTimes. Scope: appointment:read. Required: appointmentId, date.
- **Boulevard appointments reschedule** (Action). Reschedule the provided appointment to a new date and time. GraphQL mutation appointmentReschedule. Scope: appointment:write. Required: appointmentId, bookableTimeId, sendNotification.
- **Update a Boulevard appointment by ID** (Update). Update an Appointment. GraphQL mutation updateAppointment. Scope: appointment:write. Required: id.
- **Create a Boulevard arrival** (Create). Create an arrival. GraphQL mutation createArrival. Scope: appointment:write. Required: emailOrPhoneNumber, locationId.
- **Update a Boulevard booking appointment note by ID** (Update). Set appointment note for a booking. GraphQL mutation bookingSetAppointmentNote. Scope: appointment:write. Required: id, bookingClientId.
- **Update a Boulevard booking client by ID** (Update). Set client for a booking. GraphQL mutation bookingSetClient. Scope: appointment:write. Required: id, clientId.
- **Update a Boulevard booking delivery method by ID** (Update). Set the delivery method for a booking. For an in-person booking, also set where it happens. Optionally set meeting details that override the assigned staff member's own. This mutation does not check the method against the booking's services. bookingComplete checks it, so a method set here can make… GraphQL mutation bookingSetDeliveryMethod. Scope: appointment:write. Required: id, deliveryMethod.
- **Create a Boulevard booking service addon** (Create). Add a service add-on to a booking. GraphQL mutation bookingAddServiceAddon. Scope: appointment:write. Required: baseBookingServiceId, bookingClientId, bookingId, serviceId.
- **Update a Boulevard booking service duration by ID** (Update). Set durations for a given service for a booking. GraphQL mutation bookingServiceSetDurations. Scope: appointment:write. Required: id, bookingId.
- **Update a Boulevard booking service item option by ID** (Update). Updates service item options. GraphQL mutation bookingServiceUpdateServiceItemOptions. Scope: appointment:write. Required: id, bookingId, bookingServiceOptions.
- **Boulevard booking service options attach** (Action). Add service options to a given service item for a booking. GraphQL mutation bookingServiceAddServiceOptions. Scope: appointment:write. Required: bookingId, bookingServiceId, serviceOptionIds.
- **Boulevard booking service options detach** (Action). Remove service options from a given service item for a booking. GraphQL mutation bookingServiceRemoveServiceOptions. Scope: appointment:write. Required: bookingId, bookingServiceId, bookingServiceOptionIds.
- **Update a Boulevard booking service price by ID** (Update). Set the price for a given service item in a booking. GraphQL mutation bookingServiceSetPrice. Scope: appointment:write. Required: id, bookingId.
- **Boulevard booking service resources attach** (Action). Add resources to a given service item for a booking. GraphQL mutation bookingServiceAddResources. Scope: appointment:write. Required: bookingId, bookingServiceId, resourceIds.
- **Boulevard booking service resources detach** (Action). Remove resources from a given service item for a booking. GraphQL mutation bookingServiceRemoveResources. Scope: appointment:write. Required: bookingId, bookingServiceId, bookingServiceResourceIds.
- **Update a Boulevard booking service staff by ID** (Update). Set a staff member on a given service item for a booking. GraphQL mutation bookingServiceSetStaff. Scope: appointment:write. Required: id, bookingId.
- **Update a Boulevard booking service start time by ID** (Update). Set the start time for a given service item in a booking. GraphQL mutation bookingServiceSetStartTime. Scope: appointment:write. Required: id, bookingId.
- **Create a Boulevard booking service** (Create). Add a service to a booking. GraphQL mutation bookingAddService. Scope: appointment:write. Required: bookingClientId, bookingId, serviceId.
- **Delete a Boulevard booking service by ID** (Delete). Remove a service from a booking. GraphQL mutation bookingRemoveService. Scope: appointment:write. Required: id, bookingId.
- **Update a Boulevard booking start time by ID** (Update). Set start time for a booking. GraphQL mutation bookingSetStartTime. Scope: appointment:write. Required: id, startTime.
- **Boulevard bookings complete** (Complete). Complete a booking The appointment gets the delivery method set with bookingSetDeliveryMethod. When none was set, it uses the first of in person, video and phone that every service allows. Can also return: - BOOKING_DELIVERY_METHOD_NOT_ALLOWED when one or more of the booking's services do not allow… GraphQL mutation bookingComplete. Scope: appointment:write. Required: bookWithStaffId, bookingId.
- **Create a Boulevard booking** (Create). Create a booking. GraphQL mutation bookingCreate. Scope: appointment:write. Required: locationId.
- **Get single Boulevard booking by ID** (Get). Fetch booking. GraphQL query booking. Scope: appointment:read. Required: id.
- **Boulevard bookings tag** (Action). Add appointment tags to booking client for a given booking. GraphQL mutation bookingAddAppointmentTags. Scope: appointment:write. Required: bookingClientId, bookingId, tagIds.
- **Boulevard bookings untag** (Action). Remove appointment tags from booking in the context of the booking client. GraphQL mutation bookingRemoveAppointmentTags. Scope: appointment:write. Required: bookingClientId, bookingClientTagIds, bookingId.
- **Boulevard business bulk update** (Update). Update a business. GraphQL mutation updateBusiness. Scope: business:write.
- **List all Boulevard business** (List). Look up the currently authenticated business. GraphQL query business. Scope: business:read. Returns one object, not a list.
- **Update a Boulevard cart selected bookable item by ID** (Update). Update a cart's selected bookable item. Using this mutation invalidates existing reservations when the guest, staff variant, or option IDs are updated. Compared to the same mutation in the Client API, this allows the caller to change fields that are not safe to update via the Client API. For more… GraphQL mutation updateCartSelectedBookableItem. Scope: cart:write. Required: id, cart_id.
- **Get single Boulevard cart by ID** (Get). Look up a cart. GraphQL query cart. Scope: cart:read. Required: id.
- **List all Boulevard carts** (List). List Carts for a business. The Cart connection supports queries on the following fields: * id: Id * insertedAt: DateTime, in UTC timezone (Z or +0000 suffix) * updatedAt: DateTime, in UTC timezone (Z or +0000 suffix) * completedAt: DateTime, in UTC timezone (Z or +0000 suffix). GraphQL query carts. Scope: cart:read. The connector pages through all results (first / after; limit sets first, default 100).
- **Update a Boulevard client marketing setting by ID** (Update). Update a client's marketing settings. GraphQL mutation updateClientMarketingSettings. Scope: marketing:send. Required: id, type.
- **Create a Boulevard client note** (Create). Create a client note. GraphQL mutation createClientNote. Scope: client:notes:write. Required: clientId, text.
- **Delete a Boulevard client note by ID** (Delete). Delete a client note. GraphQL mutation deleteClientNote. Scope: client:notes:write. Required: id.
- **Update a Boulevard client note by ID** (Update). Update client notes. GraphQL mutation updateClientNote. Scope: client:notes:write. Required: id.
- **Update a Boulevard client reminder setting by ID** (Update). Update a client's reminder settings. GraphQL mutation updateClientReminderSettings. Scope: client:write. Required: id, type.
- **Create a Boulevard client** (Create). Create a client. GraphQL mutation createClient. Scope: client:write.
- **Get single Boulevard client by ID** (Get). Look up a client by ID. GraphQL query client. Scope: client:read. Required: id.
- **List all Boulevard clients** (List). List Clients for a business. The Client connection supports queries on the following fields: * id: Id * email: String * name: String * mobilePhone: String * active: Boolean * externalId: String * primaryLocation: Id * createdAt: DateTime, in UTC timezone (Z or +0000 suffix) * updatedAt: DateTime,… GraphQL query clients. Scope: client:read. The connector pages through all results (first / after; limit sets first, default 100).
- **Update a Boulevard client by ID** (Update). Update a client. GraphQL mutation updateClient. Scope: client:write. Required: id.
- **Create a Boulevard custom form note** (Create). Write a note against one component of a submitted form. The form must be submitted and not voided, and the component must hold no note already: a second is refused as CUSTOM_FORM_NOTE_EXISTS. GraphQL mutation createCustomFormNote. Scope: form:write. Required: componentId, content, customFormId, staffId.
- **Delete a Boulevard custom form note by ID** (Delete). Soft delete a form note, attributing the deletion to staffId. GraphQL mutation deleteCustomFormNote. Scope: form:write. Required: id, staffId.
- **Boulevard custom form reviews approve** (Approve). Sign off a submitted form by approving its review. A form signed off already answers CUSTOM_FORM_REVIEW_ALREADY_APPROVED and the first sign-off stands. One with no review to approve is refused as CUSTOM_FORM_REVIEW_NOT_REQUIRED, CUSTOM_FORM_REVIEW_NOT_RAISED or CUSTOM_FORM_REVIEW_BYPASSED. GraphQL mutation approveCustomFormReview. Scope: form:write. Required: customFormId, signatureName, staffId.
- ...and 146 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
