MCP server
Your inquiries and quotes, reachable from Claude and ChatGPT
Joinways publishes an MCP server. You connect it once. Then you ask for a date, a quote or a request — the assistant reads and writes in your workspace.
OAuth, nothing to paste
Claude, ChatGPT or Cursor open a Joinways consent screen. No API key to copy, no token to rotate.
The same tools as the app
Availability, inquiries, quotes, events, emails: seventy-two tools, the same data your team sees in Joinways.
On the Pro plan
The MCP server ships with Pro. The 30-day trial includes it, with no card.
What the MCP server does, concretely
MCP is the protocol. Claude and ChatGPT are two clients. The server is the same: mcp.joinways.app.
Ask instead of clicking around
Which room is free on 10 March for 120 people, which quotes are waiting, what came in overnight: you ask, Joinways answers from the live workspace.
Write, not only read
Draft a quote, update a status, send a follow-up from the connected mailbox. You approve the connection; the assistant does not decide on its own.
Any MCP client
Claude, ChatGPT, Cursor, or a client you build. Same URL, same OAuth, same scopes as the REST API.
What the assistant can do
- Read inquiries, events, quotes, contacts and availability
- Check which space is free for a date and a headcount
- Draft and update a quote, totals computed in Joinways
- Update an event status, with your write approval
- Send a follow-up from the mailbox already connected to Joinways
- Same OAuth scopes as the REST API: mcp.read and mcp.write
How to connect an assistant to Joinways
The short path is Claude or ChatGPT from their directories. Any other MCP client uses the same server URL.
- 1
Copy the server URL
In Joinways, open Settings, then Developers. The server address is https://mcp.joinways.app.
- 2
Paste it in your client
Claude, ChatGPT, Cursor or another MCP client: add a connector and paste that URL. Claude and ChatGPT also list Joinways in their directories.
- 3
Approve access
Joinways opens a consent screen. You sign in with your workspace and choose what the assistant may read and write.
- 4
Ask a real question
A date, a quote, the inquiries still waiting. The answer comes from your workspace, not from a demo.
Two situations where it changes the day
The date asked in the corridor
A colleague asks if 10 March is free for 120 people. You ask Claude. The answer is the live availability, not a screenshot from this morning.
The morning pass on open requests
You ask for the inquiries still waiting, quotes with no reply, events confirmed this month. One answer, from the workspace, before the first coffee is finished.
Why connect an assistant to your venue CRM?
A venue director already works in conversation: the phone, the inbox, the walk-through with the client. Typing the same facts into a CRM is the part that should disappear. An assistant connected to Joinways asks the workspace directly, so the answer is the live availability, the live quote, the live request.
MCP is the standard those assistants speak. Joinways publishes one server; Claude, ChatGPT and the rest connect to it with OAuth. You keep the relationship. The assistant prepares. You send.
And without the MCP server?
Every question about a date or a quote means opening Joinways, finding the record, reading it, then going back to the conversation you were already in.
The assistant you already use stays blind to the workspace. Joinways stays a tab you have to remember to open.
