Claude connector
Claude connected to your venue CRM
Add Joinways from the Claude directory. Then ask about a date, a quote or a request. Claude works in your workspace, after you approve.
Listed in Claude
Joinways is in the Claude directory. You add it from Claude, you do not install anything.
Your workspace, not a demo
Once you sign in and approve, Claude reads the live inquiries, quotes and availability.
You stay in charge
Claude prepares. You decide. Disconnect whenever you want, from Joinways or from Claude.
What the Claude connector does, concretely
Claude talks to the Joinways MCP server. Same data as the app, asked in the conversation you are already in.
Availability in the conversation
A date, a headcount, a room: you ask Claude. The answer comes from the live schedule, not from memory.
Quotes and requests, without switching tabs
Summarise open inquiries, draft a quote, check what is waiting for a reply. Claude stays in the thread.
The same server as ChatGPT
Claude is one client of mcp.joinways.app. ChatGPT and Cursor use the same server, the same OAuth.
What Claude can do once connected
- Read inquiries, events, quotes and availability in your workspace
- Check a date and a headcount against your rooms
- Draft a quote, with totals computed by Joinways
- Summarise requests still waiting for a reply
- Update a status or send a follow-up, if you granted write access
- Uses the Joinways MCP server at mcp.joinways.app
How to connect Claude to Joinways
The connection starts in Claude. Joinways only asks you to sign in and approve.
- 1
Open the Joinways listing
In Claude, open https://claude.ai/directory/joinways and add Joinways.
- 2
Sign in to Joinways
Claude sends you to Joinways. You sign in with the account of the workspace to connect.
- 3
Approve access
The consent screen lists what Claude may read and write. Approve, and you return to Claude.
- 4
Ask a real question
A date, a quote, the requests still waiting. Claude answers from your workspace.
Two situations where it changes the day
The brief pasted into Claude
An organiser sends a long brief. You ask Claude to match it against your rooms and your open dates. The answer is your real availability, not a guess.
The quote to reread before sending
You ask Claude to draft the quote from the request already in Joinways. You reread, you send. Nothing to retype.
Why connect Claude to your venue software?
Claude is already where a lot of the thinking happens: a draft reply, a first pass on a brief, a check before a call. If it cannot see Joinways, it invents from the last paste. Connected, it reads the live record.
The connector is the Joinways MCP server behind a Claude directory listing. You add it once. You keep the relationship with the client. Claude prepares the facts you already stored.
And without the Claude connector?
Every question to Claude needs a paste from Joinways. The paste is already stale. The next question needs another paste.
Two tools, two memories. The one that talks cannot see the one that knows.
