MCP server
Your inquiries and proposals, from Claude or ChatGPT
Joinways publishes an MCP server: you connect it once, then ask the assistant about a date, a proposal, or an inquiry. The assistant reads and writes in your workspace.
OAuth, nothing to paste
Claude, ChatGPT, or Cursor opens a Joinways consent screen, with no API key to copy, and the approval renews as long as the assistant uses it.
The same data as in the app
Availability, inquiries, proposals, events, emails: the assistant sees the same data as your team in Joinways.
Included in Pro
The MCP server is included in the Pro plan, and the 30-day trial, with no credit card, gives access to it.
What the MCP server does
Claude, ChatGPT, or another assistant connects to the same address, mcp.joinways.app, and answers with the data in your Joinways account.
Ask instead of searching
Which room is free on March 10 for 120 people, which proposals are waiting for a reply, what came in overnight: you ask the question, and Joinways answers with up-to-date data.
Write in Joinways too
The assistant can draft a proposal, change a status, or send a follow-up from the connected mailbox. Each write action is flagged as such, so the assistant can ask for your approval first.
Any MCP client
Claude, ChatGPT, Cursor, or a client you build yourself: all use the same address, the same OAuth, and the 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 moves
- Two-way: reads your workspace, writes with approved write access
- Updates
- Live: the workspace is read each time you ask
- Requirements
- 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 in Joinways
- Read inquiries, events, proposals, contacts, and availability
- Check which space is free for a date and a headcount
- Draft and update a proposal, with totals calculated in Joinways
- Update an event status, with your write approval
- Send a follow-up from the mailbox already connected to Joinways
- Never more than your role allows in Joinways
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.
Connect an assistant to Joinways
The simplest route is the Claude or ChatGPT directory; any other MCP client uses the same address.
- 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 into your client
Claude, ChatGPT, Cursor, or another MCP client: add a connector and paste that address. 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, and approve.
- 4
Ask your first question
Ask the assistant about a date, a proposal, or the inquiries still waiting: the answer comes from your real data.
The MCP server, day to day
The date someone asks about in the hallway
A colleague asks if March 10 is free for 120 people: you ask Claude, which answers with up-to-date availability.
The morning review of open inquiries
You ask the assistant for the inquiries still waiting, the proposals with no reply, and the events confirmed this month. One question is enough, and the answer comes from the workspace.
The follow-up after the site visit
After a site visit, you ask the assistant to draft the follow-up for that event. You reread it in the conversation, then ask it to send it from your mailbox.
Frequently asked questions
Why connect an AI assistant to Joinways?
An operations director already spends the day in conversation: on the phone, by email, during the site visit with the client. An assistant connected to Joinways queries your account directly: it answers with the availability, the proposal, and the inquiry as they stand right now, with nothing retyped.
MCP is the standard these assistants use: Joinways publishes a server, and Claude, ChatGPT, and the others connect to it with OAuth. You keep the client relationship: the assistant prepares, and you are the one who sends.
And without the MCP server?
Every question about a date or a proposal means opening Joinways, finding the right page, reading it, then going back to the conversation you had already started.
The assistant you already use sees nothing of your workspace, and Joinways stays one more tab to open.
What is MCP?
Model Context Protocol: the standard that lets an assistant such as Claude or ChatGPT use another piece of software, here Joinways. The Joinways server lives at mcp.joinways.app.
Do I need an API key?
Not for assistants: they register themselves, and you approve access on a Joinways consent screen. For scripts, the workspace owner or an admin can create API keys on the Pro plan.
Which plan includes it?
The Pro plan. The 30-day trial, with no credit card, gives access to Pro; after that, the MCP server stays part of the Pro plan, whatever the venue size.
Show 5 more questions
Can the assistant send emails or change a status?
Yes, if the assistant asked for write access and you approved it, as the consent screen shows. To disconnect it, remove Joinways from its connectors.
Is this the same as Zapier?
No. Zapier runs automations you defined in advance, while MCP lets you ask your questions in everyday language, when you need to. Many teams use both.
Where do I connect Claude or ChatGPT?
Claude: https://claude.ai/directory/joinways. ChatGPT: the Joinways plugin in the ChatGPT directory. Both use this same MCP server.
Does it work with Cursor or other clients?
Yes. Any client that speaks MCP over Streamable HTTP can use https://mcp.joinways.app. The workspace owner or an admin finds the JSON snippet in Settings > Developers.
How do I disconnect an assistant?
The workspace owner or an admin revokes the app in Settings > Developers > MCP > Connected apps: its access and its renewal stop. You can also remove Joinways from the assistant's connectors. Access ends on its own if you leave the workspace, or after 90 days without use (30 days for an assistant that does not renew its access).
