QuillHub

QuillHub MCP Server

Your meeting transcripts, readable by Claude, Cursor and any other MCP client.

Search past calls, read who said what, pull decisions and action items, transcribe new files and links.

Setup guide · Docs · quillhub.ai · Desktop app

---

Endpoint: https://mcp.quillhub.ai/mcp (Streamable HTTP, hosted) Auth: OAuth 2.1 with PKCE (interactive clients) or API key qai_live_... (scripts, CI) Source: this repository documents the hosted server; the server itself is operated by QuillHub. There is nothing to install or self-host.

What it is

QuillHub records meetings from your desktop without a bot in the call (Zoom, Meet, Teams, phone, in person) and transcribes uploaded files and YouTube links in 98+ languages. Every recording comes back split by speaker with timestamps, chapters, a summary, decisions and action items.

The MCP server gives your AI assistant direct access to that archive. Ask Claude "what did we agree with the client last Tuesday", "what has Anna said about pricing this month", or "transcribe this file and draft the follow-up", and it calls the right tools itself.

Quick start

Step-by-step guide with screenshots: QuillHub + Claude/Cursor via MCP.

Claude Desktop, Cursor, VS Code and other OAuth-capable clients

Point the client at the URL with no Authorization header. The client opens a browser, you sign in to QuillHub, done.

{

"mcpServers": { "quillhub": { "url": "https://mcp.quillhub.ai/mcp" } } }

Claude.ai / Claude Desktop: Settings → Connectors → Add custom connector, paste https://mcp.quillhub.ai/mcp.

Claude Code:

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

API key (headless, CI, clients without OAuth)

Get a key in the Developers dashboard (issued automatically at sign-up), then use the mcp-remote bridge:

{

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

Write Authorization:Bearer ... with no space after the colon: some mcp-remote versions split arguments on spaces.

Tools

Example prompts

• "Find every call where we discussed the migration deadline and list the decisions."
• "What did Maria commit to in last week's meetings? Quote her."
• "Transcribe https://youtu.be/... and give me the chapters with timestamps."
• "Brief me on the Acme project before tomorrow's call."
• "When did we first hear about the budget cut, and what changed after the last meeting?"

Limits and pricing

• Connecting MCP is free. Transcription uses your normal QuillHub balance: 60 free minutes on sign-up, no card. Plans at quillhub.ai/en/pricing.
• Inline base64 uploads are capped at 25 MB; for larger files pass a URL. Files up to 10 hours / 5 GB via the app.
• No webhooks over MCP. Use the REST API webhooks for push delivery.

Security and privacy

• The server is stateless and forwards your token to the QuillHub REST API; it stores no recordings and no secrets.
• Recordings are encrypted at rest and in transit, never used to train models, and can be deleted at any time.
• Don't commit real API keys into config files. Rotate keys in the Developers dashboard.

Kiro power

This repository is also a Kiro power: plugin.json, mcp.json and POWER.md sit at the root.

Also available

• REST API with webhooks: quillhub.ai/en/docs
• Desktop app for macOS 13+ and Windows 10 (2004+): quillhub.ai/en/desktop

Support

Open an issue in this repository or write to tim.nocode@gmail.com.

Privacy policy: quillhub.ai/en/legal/privacy

QuillHub is built by Axevia Labs LLC.

License

The MIT license covers the files in this repository (documentation and config examples). The hosted server at mcp.quillhub.ai is a proprietary service.