Claude

This isn't a built-in integration between Quin and Claude. It works through Quin's MCP connection: once Claude is set up as an MCP client, Quin's calendar, CRM, and contact tools become available to call from inside a Claude conversation. Everything below describes what that connection makes possible, not a Claude-specific integration Quin's team built and maintains end to end the way its CRM or calendar integrations are.

Claude is often where the open-ended thinking, drafting, and research already happens. Connecting it to Quin means a question that comes up mid-conversation, what's on the calendar this week, what a client said last time, whether a record is current, gets answered from your actual data instead of Claude's best guess.

What you can do with Claude and Quin

• Ask Claude what's on your calendar and get a real answer.
  A question like "what do I have Thursday afternoon" pulls from your connected calendar instead of anything Claude would otherwise guess at.
• Update a CRM record with a plain-language request.
  Mention that a client's number changed or a deal moved forward, and Quin makes the update the way it would if you'd asked from inside Quin directly.
• Look up a contact's history without switching tools.
  Ask what you last discussed with someone, and the answer comes from your CRM, not from what Claude remembers of the current conversation.
• Search past meetings and notes for a specific detail.
  A question about a call from a few weeks ago surfaces the same information Quin would find natively, without opening Quin to look.
• Manage Claude's API key separately from every other connection.
  Reviewing or revoking access for Claude doesn't touch the key connecting ChatGPT, Gemini, or any other MCP client.
• Bring Quin's data into a Claude project or workflow you're building.
  Anything that needs calendar, CRM, or contact context can call on Quin's tools without a separate connection to set up first.

Who this helps most

• People who already spend real time in Claude for research, writing, or analysis, since a client or calendar question gets answered right there instead of a switch over to Quin to check.
• Advisors and professionals deciding between a general assistant and Quin, who get to see what each is good at, side by side, instead of choosing blind.
• Anyone connected to more than one AI assistant through MCP, because Claude's key can be reviewed or revoked without disrupting a ChatGPT or Gemini connection running at the same time.

How this shows up day to day

• A question comes up mid-conversation in Claude.
  Instead of opening Quin to check, asking Claude directly pulls the answer from the calendar or CRM record.
• A CRM update needs to happen while working through something else.
  A plain-language request in Claude handles it the same way it would from inside Quin.
• A new workflow gets built around Claude for a specific task.
  Quin's calendar, CRM, and contact tools are available to it from the start, instead of a separate integration to build first.

Frequently asked questions

What happens when I connect Claude to Quin?
You generate an API key from Quin's MCP settings and add it to Claude as a custom connector. From there, Claude can ask Quin's calendar, CRM, and contact tools for information, and it can also make updates, like logging a note, the same way you'd ask Quin directly. Anything that would go out to another person, like an email, still waits for your review first.

Why isn't this a direct Claude integration?
Quin reaches Claude through MCP, an open standard for connecting AI assistants to outside tools, rather than a one-off integration built specifically for Claude. The result looks the same from inside a conversation: Claude can reach Quin's data. It just gets there through a shared connection method instead of code built only for Claude.

Where do I add Quin as a connector in Claude?
In Claude, open Customize, then Connectors, and add Quin as a custom connector using the server URL and API key from Quin's MCP settings. This works on Free, Pro, Max, Team, and Enterprise plans, though free accounts are limited to one custom connector at a time.

Can I use Claude and Quin at the same time?
Yes. Many people use Claude for open-ended questions, research, and drafting, and Quin for the recurring work, CRM updates, scheduled follow-ups, and reminders, that keep running whether or not a chat window is open. Connecting them means Claude can reach Quin's data the moment a question comes up, without a separate login to check it.

Is my data kept private and secure?
Yes. Quin is SOC 2 Type II certified and encrypts data in transit and at rest, the same standard applied across every integration, including MCP connections.