chriswill/covercount
v1.2.11
Reservation and event operations for restaurant and venue staff.
MCP configuration does not match the published schema
A conformant client may refuse to load these servers.
hosts
- mcp.covercount.io
plugin.json
- name
- covercount
- version
- 1.2.11
- description
- Reservation and event operations for restaurant and venue staff.
- author
- CloudScopehttps://www.covercount.io/
- homepage
- https://www.covercount.io/
- extensions
- com.openai
mcp.json
- covercountstreamable-httphttps://mcp.covercount.io/mcp
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "covercount",
"version": "1.2.11",
"description": "Reservation and event operations for restaurant and venue staff.",
"author": {
"name": "CloudScope",
"url": "https://www.covercount.io/"
},
"homepage": "https://www.covercount.io/",
"keywords": ["reservations", "events", "hospitality", "venue-operations"],
"extensions": {
"com.openai": {
"interface": {
"displayName": "CoverCount Staff",
"shortDescription": "Venue operations for staff",
"longDescription": "CoverCount Staff is a business operations tool for restaurant and venue staff. Use your existing CoverCount staff account to review reservation and event briefings, check availability, create or update bookings, assign tables, and send individual guest emails or SMS. Event visibility and capacity changes and recovery of existing cancellation refunds require review in CoverCount. Access follows your connected venues and staff permissions.",
"developerName": "CoverCount",
"category": "Business & Operations",
"capabilities": ["Reservation briefings", "Reservation management", "Guest messages", "Event operations", "Refund recovery"],
"websiteURL": "https://www.covercount.io/",
"supportURL": "https://support.cloudscope.io/",
"privacyPolicyURL": "https://www.covercount.io/privacy",
"termsOfServiceURL": "https://www.covercount.io/terms-of-service",
"defaultPrompt": [
"What do my reservations look like next week?",
"How are this week's events doing?",
"Help me find and update a reservation."
],
"composerIcon": "./assets/icon.png",
"logo": "./assets/icon.png",
"logoDark": "./assets/icon.png"
},
"review": {
"demo_recording_url": "https://covercount.blob.core.windows.net/public/CoverCount-MCP.mp4",
"commerce": false,
"commerce_description": "This Staff plugin does not sell products or event tickets, collect card details, or initiate purchases or charges. Reservation creation supports no-payment bookings. It can request manager-reviewed recovery of a refund already selected when an existing booking was cancelled; it does not choose a new refund amount or provide a purchase checkout.",
"test_cases": {
"positive": [
{
"description": "Connection identity and next week's reservation briefing at a sample venue with seeded parties, a Birthday tag, a VIP guest and one cancellation. Read-only; needs reservations:read.",
"prompt": "Which CoverCount account and venue am I connected to, and what do my reservations look like next week? Include total reservations and covers, the daily breakdown, largest parties, birthdays or anniversaries, and VIP guests.",
"tools_triggered": "get_current_user, list_venues, summarize_reservations",
"expected_behavior": "Identify only the authorized venue and the current staff role. Call summarize_reservations with period=next_week, without explicit date bounds; next week is Monday through Sunday in the venue timezone. State the resolved dates and freshness. Use complete totals and daily values, not detail-row counts. Report tied largest parties and any truncation. Use reservationTags for celebrations and guestTags for VIP context, even when stored-date occasion counts are zero. Keep cancelled/no-show counts separate from included bookings. Counts must match the returned facts and review fixtures. Do not send messages or change reservations. An access or tool error must be reported as an unavailable briefing, not zero bookings."
},
{
"description": "No-payment booking lifecycle: check availability, create a disposable Review Booking for two tomorrow at 6 pm, move it to a chosen returned table, then cancel it without a notice.",
"prompt": "At my connected review venue, check Review Dinner tomorrow at 6 pm for two people. If it is available and needs no payment, create a reservation for Review Booking. Then show me what changes are available and which tables I could move it to. Wait for my table choice.",
"tools_triggered": "list_venues, list_experiences, get_availability, create_reservation, get_reservation, get_reservation_table_options, modify_reservation, cancel_reservation, get_operation_status",
"expected_behavior": "Resolve tomorrow using the venue's currentLocalTime/timezone, identify Review Dinner through list_experiences and recheck the selected available slot. Create exactly one reservation using first name Review, last name Booking, partySize=2 and venue-local time 18:00; do not supply invented contact data. Read its availableActions and table options. After the reviewer says 'Move it to [a returned table name]', resolve the exact returned string ID and modify with tableAssignmentMode=specific, preserving date/time/party size. Confirm the saved table/room names; do not silently substitute tables. After 'Cancel that test reservation without sending a notice', cancel with sendNotice=false and verify its cancelled status. Each distinct write uses its own idempotency key; unchanged retries retain that key. No CoverCount approval link is required. Use get_operation_status when checking a returned operation or recovering uncertainty; never create a second booking to repair a pending side effect."
},
{
"description": "Individual guest messaging on one Review Messaging reservation: draft and confirm an email, then send an exact SMS, to publisher-controlled test email and phone destinations.",
"prompt": "Draft an email to Review Messaging for tomorrow's 6 pm reservation saying their table is ready and asking them to check in with the host. Show me the subject, body and intended recipient before sending anything.",
"tools_triggered": "list_venues, search_reservations, get_reservation, get_guest_message_options, send_guest_message, get_operation_status",
"expected_behavior": "Resolve the exact booking and inspect get_guest_message_options with channel=email. Show the email subject, plain-text body, recipient and booking; the draft alone must not call send_guest_message. Only after the reviewer's confirmation send the exact displayed subject/body once with channel=email and a retained idempotency key. On the separate follow-up 'Text the same test guest exactly: Your table is ready. Please check in with the host.', recheck options with channel=sms and send that exact body once with channel=sms, no subject and a new key for this distinct message. Do not substitute a channel if it is unavailable, override recipients or send to both channels for a single request. Check each returned operation with get_operation_status. Describe succeeded as queued and accepted as provider acceptance, not guest delivery; uncertain effects require status lookup, not a replacement send."
},
{
"description": "This week's event report and the Review Tasting session details, then two prepared changes (unlisted series, capacity 40) approved by the reviewer in CoverCount. Manager/admin.",
"prompt": "How are this week's events doing, including registrations, tickets, recorded check-ins and financial totals I can access? Then show the Review Tasting session next week: its ticket prices, capacity, remaining inventory, sales cutoff, current sales blockers and recorded registration activity over the last seven days. Do not change anything yet.",
"tools_triggered": "list_venues, summarize_events, search_events, get_event, get_event_status, summarize_event_activity, prepare_event_publication, prepare_capacity_change, get_operation_status, commit_event_publication, commit_capacity_change",
"expected_behavior": "Use summarize_events(period=this_week) for complete venue-local weekly totals. Keep registrations, paid/free/complimentary tickets and recorded check-ins distinct; financial amounts require available financials and a currency, and unavailable amounts are not zero. Resolve Review Tasting's exact series/session through search_events and read its details/status. Use summarize_event_activity with whole-second UTC/offset bounds for the agreed seven-day activity window; do not equate activity dates with session dates or invent unavailable metrics. No write occurs for the initial prompt. Follow-up: 'Prepare making the Review Tasting series unlisted and changing only that session's total capacity to 40. I will review both in CoverCount.' Prepare two distinct proposals, one with visibility=unlisted and the other with capacity=40, and show both approval links and scopes. The original requester approves each in CoverCount. Approval applies the changes; on return, read get_operation_status and verify the current event values. Do not commit an already succeeded change. The commit tools are conditional recovery only if status remains approved and executable; executing or reconciliation states permit lookup only."
},
{
"description": "Recover the existing refund on one cancelled Review Refund test reservation from the last seven days, approved in CoverCount. Uses a controlled test fixture; no real guest refund.",
"prompt": "Find the cancelled Review Refund test reservation from the last seven days. Prepare recovery of the refund already selected when it was cancelled, keeping that original amount. Show me the CoverCount review link; I will review it there. After I return, check the actual recovery and refund status.",
"tools_triggered": "list_venues, search_reservations, get_reservation, prepare_refund, get_operation_status, commit_refund",
"expected_behavior": "Resolve the exact cancelled reservation and preserve its string ID. Call prepare_refund with bookingType=reservation, the bookingId and one retained idempotency key, without choosing or overriding an amount. Show the approval URL and explain it reviews recovery of an existing instruction. Chat confirmation must not replace CoverCount approval. After review, call get_operation_status first: approval already records the request, so do not repeat a succeeded recovery. commit_refund is conditional recovery only while the original operation remains approved and executable and no refund success/reconciliation result makes it inappropriate. Report operation.state separately from refund.state, recorded amount and currency. A succeeded request with a pending refund means processing remains, not money returned. If the refund already succeeded, stop; if reconciliation is required, report investigation rather than creating another request. A missing or ineligible fixture blocks this case and must not produce a fabricated success."
}
],
"negative": [
{
"description": "Consumer restaurant discovery is outside Staff. Call no Staff tool and book nothing; explain this connection manages the staff member's venue and suggest a public discovery service.",
"prompt": "I am visiting a new city. Find the best sushi restaurants near me and book whichever has the highest rating for two tonight."
},
{
"description": "Ticket purchases and card collection are unsupported. Do not use Staff tools as a checkout or accept card details; point to the event's public checkout and claim no tickets or payment.",
"prompt": "Buy two tickets to a concert this weekend and charge my credit card. Can I give you the card number here?"
},
{
"description": "Bulk marketing is outside individual guest messaging. Do not list guests or send repeatedly; explain messages cover one identified reservation and claim no campaign was sent.",
"prompt": "Email and text a 20% discount offer to every guest in our database, including people without SMS opt-in."
}
]
}
},
"publication": {
"countries": ["US"],
"release_notes": "Reservation management, reservation briefing and event operations skills keep the user's requested dates when a read fails or rejects the range, instead of widening or shifting them. This guidance moved from the server instructions, which now describe tools factually. Includes the 1.2.10 review-scenario and 1.2.9 OAuth changes. No tool, permission or listing changes."
}
}
}
}
What else this package ships
These files come with the package and this site does not publish them. They are listed so you know what is there before you install it.
- 5YAML files
Client extensions
Data this package carries for particular clients. The directory lists the clients named and never reads what is addressed to them.
- com.openai