Claude connector
Claude connected to your venue CRM
Add Joinways from the Claude directory. Then ask about a date, a proposal 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, proposals and availability.
You stay in charge
Claude prepares and you decide. You can disconnect from Claude whenever you want.
What the Claude connector does
Claude talks to the Joinways MCP server. You get the same data as in the app, in the conversation you are already having.
Availability in the conversation
A date, a headcount, a room: you ask Claude. The answer comes from the live schedule.
Proposals and requests, without switching tabs
Summarize open inquiries, draft a proposal, 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.
At a glance
- Category
- Automation and AI assistants
- Availability
- Available
- Setup time
- About 2 minutes
- Who can connect
- Any workspace member, from their own Claude account
- What flows where
- Two-way: reads your workspace, writes with approved write access
- Updates
- Live: Claude reads the workspace at each question
- Needed on the tool's side
- A Claude account that can add directory connectors
- Built by
- Joinways (native integration)
Before you start
- A Joinways workspace on the Pro plan or in its 30-day trial.
- A Claude account that can add connectors from the Claude directory.
- A Joinways login that is a member of the workspace you want to connect.
What Claude can do once connected
- Read inquiries, events, proposals and availability in your workspace
- Check a date and a headcount against your rooms
- Draft a proposal, with totals computed by Joinways
- Summarize 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
Security and access
- The consent screen lists what Claude asks for: reading your workspace, and creating or updating records.
- 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, Claude only reads.
- Each approval covers one workspace and renews as long as Claude uses it. After 90 days without use, you approve again.
- Access stops if you leave the workspace or if the workspace is no longer on Pro or in trial.
- What Claude reads becomes part of your Claude conversation. The records themselves stay in Joinways.
What it does not do
- The consent screen does not offer a read-only switch: you approve what Claude asks for, or decline.
- It does not stay connected behind your back: Claude is listed in Settings → Developers → MCP → Connected apps, where the workspace owner or an admin can disconnect it.
- Access is not open-ended: after 90 days without use, Claude needs your approval again.
- It acts only when you ask Claude. It does not watch your workspace in the background.
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 proposal, the requests still waiting. Claude answers from your workspace.
Where it helps day to day
The brief pasted into Claude
An organizer sends a long brief. You ask Claude to match it against your rooms and your open dates. The answer is checked against your real availability.
The proposal to reread before sending
You ask Claude to draft the proposal from the request already in Joinways. You reread it and send it without retyping anything.
The status check before a call
Before calling a client, you ask Claude where their event stands: status, open proposal, last emails. The answer comes from the event in Joinways.
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 works from whatever you last pasted; once connected, it reads the live record.
The connector is the Joinways MCP server behind a Claude directory listing. You add it once, and Claude works from the inquiries, proposals and availability already in your workspace.
And without the Claude connector?
Every question to Claude needs a paste from Joinways that is already out of date, and the next question needs another one.
Claude and Joinways each keep their own memory, and Claude cannot see what is in your workspace.
