Quinbook
Talk to your quinbook ticketing system in plain language — bookings, slots, calendar, contacts, coupons and cart/order operations as tools for Claude.
- Category
- Commerce
- Primary Subcategory
- Calendar & Scheduling Apps
View in the Claude registryIntegration details
Description
MCP server exposing the quinbook API. Read tools for slots, orders, coupons and contacts; write tools for cart, order lifecycle and contacts that execute immediately (the bundled skills require confirming with the user first). OAuth login with your own quinbook credentials; multi-tenant via me_switch_company.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Calendar & Scheduling Apps
- Secondary Subcategories
- None listed
- Brand
- QuinBook
- Access
- Unknown
- First tracked
- 2026-06-21
- Tool count
- 0
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Get alerts for Quinbook
Get updates when Quinbook’s Discoverability Score or category rank changes.
Claude Discoverability Score
Quinbook isn’t discoverable through Claude’s Connector picker
It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What the current score measures
Remote Connectors Claude can surface from the Connector picker.
0 tools agents can invoke
No tools are exposed by this Claude Connector in the latest snapshot.
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.