Quanfire.aiMCPNew
MCP integration · Live

Bring your Quanfire workspace
into any AI assistant

Quanfire connects over the open Model Context Protocol (MCP) — so Claude, or any MCP-compatible assistant, can answer questions across all seven products in plain English (and, with write access enabled, act on them), straight from your live workspace.

Start free trialHow to connect

Already a customer? Add the MCP server mcp.quanfire.ai/mcp in your assistant.

Connected in under a minute

No engineering, no API keys — sign in with the account you already have.

01

Add the connector

In your AI assistant, add a custom MCP server pointing to mcp.quanfire.ai/mcp.

02

Sign in & approve

Log in with your existing Quanfire account and approve access on a consent screen. Your role carries over.

03

Just ask

Ask across all 7 products in plain English. Quanfire answers from your live workspace — no copy-paste, no exports.

One assistant, all seven products

Ask in plain English — Quanfire pulls the answer from the right product.

📄
DocPro

“Show my documents and their confidence scores.”

⏱️
BillAI

“List this month's time entries and open matters.”

🧠
MindMap

“Who are my flight-risk people right now?”

📊
DataSense

“What did my key numbers look like last quarter?”

🎯
HireIQ

“Show candidates for the senior associate role.”

🚀
GrowthAI

“List my latest marketing content.”

⚙️
FlowOS

“Give me a snapshot across my workspace.”

Live proof

Don't take our word for it

The retrieval behind these answers runs on our own multilingual embedding model. Verify it yourself in your browser — search one meaning across 15 languages and watch our adapter separate signal from noise. Nothing cached; every score computed live.

Try the live embeddings demo →

Secure by design

You stay in control — sign in with your own login, approve access, revoke anytime.

🔐

OAuth 2.0 sign-in

You authenticate with your own Quanfire login and approve access on a consent screen — no API keys to copy or paste around.

👁️

Read by default, write on request

Out of the box your assistant reads and queries your workspace. A workspace admin can switch on write access (create, edit, delete) — and it still obeys each user's role.

🛡️

Role-aware

Access follows your Quanfire role. Viewers stay read-only, and tenant isolation is always enforced server-side.

🚫

Never trains AI

Your workspace data is never used to train models, and you can revoke access at any time.

🧩

Scoped to your plan

The assistant only sees tools for the products your workspace actually has — nothing you're not subscribed to.

Connect it to your assistant

Example: Claude Desktop. Any MCP client follows the same idea — add the URL as a custom MCP server.

  1. 1Open Settings → Connectors and choose Add custom connector.
  2. 2Name it Quanfire and paste the URL https://mcp.quanfire.ai/mcp.
  3. 3A browser opens — sign in with your Quanfire account and click Allow access.
  4. 4Done. Ask something like “show me my DocPro items” and it answers from your workspace.

Built on the open Model Context Protocol — works with Claude and any MCP-compatible assistant.

Beyond reading: with write access enabled by your workspace admin, your assistant can also create and update records on your behalf — log time, add a candidate, update a node — always within each user's role (Viewers stay read-only).

Bring your firm's data into your AI

Start a free trial, then connect Quanfire to your AI assistant in under a minute.

Start free trialSee pricing