MCP server
Your inquiries and proposals, reachable from Claude and ChatGPT
Joinways publishes an MCP server that you connect once. After that, you ask about a date, a proposal or a request, and 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. The approval renews as long as the assistant uses it.
The same tools as the app
Availability, inquiries, proposals, events, emails: 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
MCP is the protocol, and Claude and ChatGPT are two of its clients; both connect to the same server, mcp.joinways.app.
Questions in plain language
Which room is free on March 10 for 120 people, which proposals are waiting, what came in overnight: you ask, Joinways answers from the live workspace.
Write, not only read
Draft a proposal, update a status, send a follow-up from the connected mailbox. Each write action is marked as such, so the assistant can ask you before running it.
Any MCP client
Claude, ChatGPT, Cursor, or a client you build. Same URL, same OAuth, same scopes as the REST API.
At a glance
- Category
- Automation and AI assistants
- Availability
- Available
- Setup time
- About 2 minutes
- Who can connect
- Any workspace member, for the workspace they pick, with the rights of their role
- What flows where
- Two-way: reads your workspace, writes with approved write access
- Updates
- Live: each question reads the workspace at that moment
- Needed on the tool's side
- An MCP client with Streamable HTTP and OAuth, or an API key
- Built by
- Joinways (native integration)
Before you start
- A Joinways workspace on the Pro plan or in its 30-day trial.
- An MCP client that connects over Streamable HTTP. Clients limited to the older SSE transport are not supported.
- A Joinways login that is a member of the workspace you want to connect.
- For a script with an API key: the workspace owner or an admin creates the key in Settings, Developers.
What the assistant can do
- Read inquiries, events, proposals, contacts and availability
- Check which space is free for a date and a headcount
- Draft and update a proposal, 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
Security and access
- Two access levels: read (mcp.read) and create or update (mcp.write). The consent screen lists the ones the assistant asks for.
- Write access includes sending emails from your mailbox or a shared team mailbox, and deleting records such as proposals or tasks. Everything follows your role in the workspace: with Read-only, the assistant only reads.
- Each approval covers one workspace and renews as long as the assistant uses it. After 90 days without use (30 days for an assistant that does not renew its access), you approve again.
- Access stops if you leave the workspace or if the workspace is no longer on Pro or in trial.
- Joinways stores only a fingerprint of each access token, never the token itself, and logs every use.
What it does not do
- The consent screen does not offer a read-only switch: you approve what the assistant asks for, or decline.
- It does not stay connected behind your back: each connected assistant is listed in Settings → Developers → MCP → Connected apps, where the workspace owner or an admin can disconnect it.
- Access is not open-ended. An assistant that renews its access on its own asks for your approval again after 90 days without use; the others, after 30 days.
- It acts only when you ask the assistant. Nothing runs in the background or on a schedule.
- Calls are capped per minute and per day for each workspace, with a tighter cap on sending emails.
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
The server address is https://mcp.joinways.app. The workspace owner or an admin also finds it in Settings, Developers.
- 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, pick the workspace, read what the assistant asks for, then approve.
- 4
Ask a real question
Ask about a date, a proposal or the inquiries still waiting, and the answer comes from your own workspace.
Where it helps day to day
The date asked in the corridor
A colleague asks if March 10 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, proposals with no reply, events confirmed this month. You get a single answer, straight from the workspace.
The follow-up after the site visit
After a walk-through, you ask the assistant to draft the follow-up for that event. You reread it in the conversation, then ask it to send from your mailbox.
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. An assistant connected to Joinways asks the workspace directly, so the answer reflects the current availability, proposal or request, with nothing retyped.
MCP is the standard those assistants speak. Joinways publishes one server; Claude, ChatGPT and the rest connect to it with OAuth. You keep the client relationship: the assistant prepares, and you decide what gets sent.
And without the MCP server?
Every question about a date or a proposal means opening Joinways, finding the record, reading it, then going back to the conversation you were already in.
The assistant you already use cannot see the workspace, and Joinways remains a tab you have to remember to open.
