MCP

Most integrations connect Quin to a single tool. MCP works the other way, letting any MCP-compatible AI assistant, Claude, ChatGPT, or another client, call on Quin's tools directly, so calendar, CRM, and contact data become available without leaving the assistant you're already using.

What you can do with MCP and Quin

• Search your calendar and meetings from inside Claude, ChatGPT, or another MCP client.
  The answer comes back without switching over to Quin directly.
• Update CRM records and contacts using a plain-language request.
  It works the same way it would from inside Quin itself.
• Ask a question and get raw data back directly in your AI assistant.
  There's no extra step to open a separate app to see the result.
• Create separate API keys for each tool or client that connects.
  Managing access for one doesn't affect any of the others.
• Revoke a single API key without disconnecting the rest.
  Access can be scoped down to exactly the client that needs it.
• Bring Quin's toolset into a custom or internal AI workflow.
  Any MCP-compatible client can call on the same actions Quin uses natively.

Who this helps most

• Teams already working inside Claude, ChatGPT, or another MCP-compatible assistant, who want Quin's data available without switching tools.
• Technical and ops-minded users building custom AI workflows, where Quin's actions can slot in as one capability among several.
• Anyone managing access across multiple AI tools, since separate API keys keep each connection scoped and easy to revoke.

How this shows up day to day

• A question about today's schedule comes up inside a different AI assistant.
  Asking it there returns the answer without switching over to Quin.
• A CRM update needs to happen mid-conversation in another tool.
  A plain-language request handles it the same way it would inside Quin directly.
• Rolling out Quin to a new AI client or workflow.
  A separate API key for that connection keeps it scoped, so revoking it later doesn't affect anything else.

Frequently asked questions

What happens when I connect MCP?
Quin's tools, calendar, CRM, contacts, and more, become available to call from any MCP-compatible AI assistant using an API key you generate.

Which AI assistants work with MCP?
Any client that supports the Model Context Protocol, including Claude and ChatGPT, can connect to Quin this way.

Can I manage access separately for different tools?
Yes. Each tool or client gets its own API key, so access can be reviewed, scoped, or revoked individually without affecting other connections.

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, not just MCP.

Does Quin replace my AI assistant?
No. Quin adds its tools and data to the assistant you're already using. The assistant itself still handles the conversation.