QuillHub

ai.quillhubPublished by quillhub.aiOfficial publisherv1.0.1Updated Oct 27, 2026

Meeting transcripts for AI agents: search calls, read who said what, transcribe files and links.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & MemoryCommunication & Collaboration

Overview

AI-generated overview

Hosted MCP server that gives an assistant searchable access to your QuillHub meeting transcripts, speaker quotes, decisions and action items.

What you can do
  • Search and list recordings across workspaces and projects, with summaries, decisions, action items and participants
  • Read a single recording as summary, full text, speaker segments, dialog, paragraphs, chapters or subtitles
  • Pull timestamped quotes from one person across meetings, filtered by date and project
  • Browse tracked subjects (people, deals, projects, clients) with living notes, open commitments and a revision timeline
  • Surface open questions and contradictions, and read AI-maintained project briefings
  • Transcribe a URL or an inline file, then wait for or cancel the job
When to use it
Useful when your meetings are recorded in QuillHub and you want an assistant to answer questions about past calls, quote what someone said, prepare briefings before a meeting, or transcribe a new file or link without leaving the chat.
Requirements
Remote hosted endpoint over Streamable HTTP; nothing to install or self-host. Authentication is required: OAuth 2.1 with PKCE for interactive clients, or an API key passed as an Authorization Bearer header for headless clients, typically through the mcp-remote bridge. A QuillHub account is needed.
Before you install
The assistant can read your whole meeting archive, including teammates' shared recordings, so scope access deliberately. Transcription spends your QuillHub balance (60 free minutes at sign-up, then paid plans). Creating transcriptions sends URLs or uploaded files to QuillHub. Keep API keys out of committed config files and rotate them in the dashboard.

Installation

In SourceWeft

  1. Open QuillHub in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.quillhub%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

[QuillHub logo]

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.

json
{  "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:

bash
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:

json
{  "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

ToolWhat it does
search_meeting_transcriptsFull-text search across meetings in a workspace: titles, summaries, decisions, action items and transcript text. Morphological matching in English and Russian.
list_transcriptionsPaginated list of recordings with summary, key theses, decisions, action items, participants, project. Filter by text, date range, workspace, project.
get_transcriptionOne recording in the format you need: summary, text, segments, dialog (who said what), paragraphs, chapters, subtitles. Supports time windows for long calls.
get_person_speechTimestamped quotes from one person across every meeting, with filters by date and project.
find_subjectsFind tracked subjects (people, deals, projects, clients, candidates, custom types) with their AI-maintained note, open commitments and mention counts.
get_subject_pageFull page for one subject: living note, open commitments, every meeting mention with quotes and speakers, unresolved questions.
get_state_timelineHow a subject's note changed over time: revisions with diffs and the recording that caused each change.
list_open_questionsContradictions and ambiguities the AI found across meetings (e.g. two different budget figures) that need a human decision.
get_project_memoryAI-maintained briefing for a project or workspace: purpose, glossary, key people, activity digest.
list_subject_typesSubject types available in a project and the fields each one tracks.
list_workspacesYour workspaces and the projects inside them, so the agent can read teammates' shared recordings.
create_transcriptionTranscribe a URL (YouTube, direct file link) or an inline base64 file up to 25 MB.
wait_for_transcriptionWait for a job to finish (up to 300 s per call), no polling loop needed.
cancel_transcriptionCancel a queued or running job.
get_accountAccount, balance and subscription. Cheap liveness check.
get_developer_docsQuillHub developer docs as markdown, for agents writing integration code.

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

Support

Open an issue in this repository or write to [email protected].

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.

Source: README.md at commit 204dc46

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 23, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts