Connect QuillAI to Claude and Cursor via MCP

Connect the QuillAI knowledge base to Claude and Cursor in one click via OAuth — or with an API key for headless setups: buttons, configs, and step-by-step instructions.

Why connect

MCP (Model Context Protocol) is an open standard that lets AI assistants see and call external tools. With the QuillAI MCP server connected, you can ask questions about your recordings right from your usual assistant chat — no copy-pasting back and forth.

What you can ask

“What did we promise client X in the last meeting?” — the assistant finds the right recording and quotes the commitment.
While working in Cursor — “Pull in the context from the call about this feature” — the assistant brings meeting decisions straight into code review or a task description.
In Claude — “Summarize all my meetings this week” — the assistant lists the recordings for the period and distills the highlights.

One-click connect

The QuillAI MCP server supports OAuth, so you no longer need an API key: click the button, confirm the connector, and sign in to your account. The connector appears under the name “QuillHub”.

Claude (Web and Desktop)

→ Add to Claude

Open the link

The link above opens claude.ai with the “Add custom connector” dialog already prefilled — no need to type the name or server URL.

Confirm

Click Add, then Connect next to the new QuillHub connector.

Authorize

Sign in to your QuillAI account and grant access. The connector becomes available in Claude Web, Claude Desktop, and Cowork.

Cursor

→ Add to Cursor

Open the link

The cursor.com page will offer to open Cursor and install the QuillHub MCP server — confirm the install.

Authorize

Cursor runs the OAuth flow itself: sign in to your QuillAI account in the browser window that opens. No keys or configs needed.

Claude Code

claude mcp add --transport http quillhub https://mcp.quillhub.ai/mcp

Run the command in your terminal, then type /mcp inside Claude Code, pick quillhub → Authenticate — a browser window opens for sign-in. Tokens refresh automatically.

Manual setup (other MCP clients)

Any client that supports remote MCP with OAuth connects via the server URL:

https://mcp.quillhub.ai/mcp

Open connector settings

For example, in claude.ai: Settings → Connectors → Add → Add custom connector.

Paste the server URL

Use any name, e.g. QuillHub; paste the URL above into the URL field. Leave the OAuth Client ID and Client Secret fields empty.

Confirm and authorize

Click Add, then Connect — and sign in to your QuillAI account.

The Add custom connector dialog in claude.ai with the QuillAI MCP server URL

Alternative: API key

For headless/CI setups and clients without OAuth support, the API-key method still works. Create a qai_live_... key under Settings → Integrations and use this config:

{
  "mcpServers": {
    "quillai": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.quillhub.ai/mcp",
        "--header",
        "Authorization:Bearer qai_live_YOUR_KEY"
      ]
    }
  }
}

⚠️

No space after the colon

Write Authorization:Bearer qai_live_..., not Authorization: Bearer qai_live_.... Some versions of mcp-remote split the argument on the space and lose part of the token.

⚠️

Protect your key

The MCP server forwards the Authorization header verbatim to the REST API. Don't save or commit a config with a real key value to a public repository.

Technical details

The full tool list, limits (e.g. the 25 MB inline-file cap), and an example of a direct HTTP call without an MCP client are in the developer docs at /docs/mcp.