Connectors
Connect Excellent to Claude
Last reviewed September 25, 2026
1. What the connector does
The Excellent connector lets Claude — or any assistant that speaks the Model Context Protocol (MCP) — answer questions from your restaurant group’s live Excellent data: events and bookings, inbound leads, invoices and deposits, documents, rooms, contacts, the marketing queue, and the group events report with pace against your revenue goal. With draft access it can also stage a thank-you card, a social post or a guest email campaign into your review queues. It never publishes, sends, changes or deletes anything; a person on your team always approves first.
Amounts are returned in minor units (cents). Each connection sees exactly one organization — the one the approving administrator chose.
2. Connecting
You need: an Excellent account with the administrator role in the organization you want to connect. Only administrators can approve a connection.
In Claude: open Settings → Connectors, find Excellent in the directory and choose Connect. (If you are adding it yourself as a custom connector, use the server URL https://beexcellent.ai/api/mcp.) Claude sends you to Excellent: sign in, review what the assistant is asking for, and choose Approve. You return to Claude connected. The approval card names the site Approve sends you back to — for Claude, claude.ai. If it names a site you didn’t just come from, choose Cancel: any app can call itself “Claude”, but only Claude returns you to claude.ai.
Access levels. Read lets the assistant answer questions from your data. Draft additionally lets it stage drafts for your review. You choose on the consent screen: read access is always included, and “Also allow drafts” is yours to tick or leave off.
Other MCP clients. Clients that support MCP authorization connect the same way. For a client that only accepts a bearer token, an administrator can mint a scoped, expiring token under Settings → AI assistant access in Excellent.
3. Tools
The connector exposes a fixed, reviewed set of tools. It has no free-form query tool and cannot run arbitrary database queries.
| Tool | Access | What it does |
|---|---|---|
Group overviewoverview | Read | Snapshot of this restaurant group: locations, upcoming events, new leads, outstanding balance. |
List eventslist_events | Read | Events (bookings) with status, date, time window, party size, location and room. |
List leadslist_leads | Read | Inbound inquiries (leads) with contact info, status, requested date and party size. |
List invoiceslist_invoices | Read | Invoices with totals, deposit due, amount paid, and the linked event. |
List documentslist_documents | Read | Documents (proposals, BEOs, contracts, training content) with status and version. |
List rooms and spaceslist_spaces | Read | Bookable rooms/areas with capacity and location. |
List contactslist_contacts | Read | Contacts (hosts/clients) with reach info and event counts. |
Marketing queue statusmarketing | Read | Marketing queue status, both lanes: recent social posts (channel, status, slot, send fact + link) and guest campaigns (kind, segment, status, slot, send progress — sent/suppressed/failed of total). The read-side answer to what became of a draft_marketing_post or draft_marketing_campaign draft; needs only the 'read' scope. |
Draft a thank-you carddraft_thank_you_card | Draft (needs draft access) | DRAFT a thank-you card for one event from its facts + the guest photo wall. Writes a reviewable DRAFT only — it never publishes to guests; the operator reviews and publishes it from the event page. Requires a token minted with the 'draft' scope. Returns what was staged (nothing is sent). |
Draft a social postdraft_marketing_post | Draft (needs draft access) | DRAFT one social post (instagram or linkedin) for this group's marketing review queue, grounded ONLY in the org's own events and published recaps (every claim is quote-verified against them). Writes a reviewable DRAFT — it never approves and never publishes; the operator approves in Portfolio → Marketing and the engine sends behind the org's live gate. Requires a token minted with the 'draft' scope. Returns what was staged (nothing is sent). |
Draft a guest email campaigndraft_marketing_campaign | Draft (needs draft access) | DRAFT one bilingual (en/es) guest-campaign email for this group's marketing review queue, grounded ONLY in the org's own completed events and published recaps (every claim is quote-verified against them). Writes a reviewable DRAFT — it never approves and never sends; the operator approves in Portfolio → Marketing and only the consent-gated engine emails the segment. Requires a token minted with the 'draft' scope. Returns what was staged (nothing is sent). |
Events reportreport | Read | Aggregated Events report for the whole group over a period: revenue (booked/collected/outstanding), booking pace vs last period with a plain-language on-track verdict and % to the annual goal, pipeline by stage + win rate, lead funnel, booking sources, and the per-location rollup. Amounts in minor units (cents). |
4. Things to ask
- “What does the next two weeks of private events look like across all our locations?”
- “Which new leads haven't been contacted yet, and what dates and party sizes are they asking about?”
- “How are we pacing against this year's events revenue goal, and which location is behind?”
- “Which invoices still have a deposit outstanding?”
- “Draft a thank-you card for last Saturday's rehearsal dinner.”
- “Draft an Instagram post about our patio room using our recent events.”
5. Access, safety and your data
Scoped to your organization. Every tool call is answered by a database function that resolves your organization from the connection’s credential; nothing in a request can widen it to another organization’s records.
Drafts only. The draft tools add a new item to a review queue. Publishing a post, sending a campaign or sharing a card happens only when someone on your team approves it in Excellent, and campaigns go only to guests who consented to receive them.
Short-lived credentials. Connections use OAuth 2.1 with PKCE. Access tokens expire after one hour and refresh credentials rotate on every use; we store only one-way hashes of them.
Your conversations stay with the assistant. Excellent receives only the parameters of each tool call (for example, a status filter), never your conversation. How we handle connection data is set out in our Privacy Policy; our security controls are described on the Security page.
6. Disconnecting
An administrator can see every connected assistant, when it was approved and when it was last used, under Settings → AI assistant access in Excellent, and revoke any of them there; revoking ends its access immediately. You can also remove the connector from Claude under Settings → Connectors.
7. Troubleshooting and support
- “You need to be an administrator” — approve the connection while signed in as an administrator of that organization, or ask one to connect.
- A draft tool says it needs draft access — disconnect and reconnect, and tick “Also allow drafts” on the consent screen.
- The connector stopped working — it may have been revoked under Settings → MCP; reconnect from Claude.
Anything else: email support@beexcellent.ai.