FunASR vs QuillHub — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
FunASR vs QuillHub
In-depth architectural comparison of the FunASR and QuillHub MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
FunASR
Speech-to-Text · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
QuillHub
Speech-to-Text · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose FunASR if you need specialized Speech-to-Text tools running via a local process. Choose QuillHub if your workspace requires Speech-to-Text integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose FunASR when:
You need dedicated capabilities in the Speech-to-Text domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
No explicit tool names declared in metadata yet. Check project README on main listing page.
QuillHub Tools (16)
search_meeting_transcripts
Full-text search across meetings in a workspace: titles, summaries, decisions, action items and transcript text. Morphological matching in English and Russian.
list_transcriptions
Paginated list of recordings with summary, key theses, decisions, action items, participants, project. Filter by text, date range, workspace, project.
get_transcription
One recording in the format you need: `summary`, `text`, `segments`, `dialog` (who said what), `paragraphs`, `chapters`, `subtitles`. Supports time windows for long calls.
get_person_speech
Timestamped quotes from one person across every meeting, with filters by date and project.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
FunASR is categorized under Speech-to-Text and uses a local stdio subprocess. In contrast, QuillHub belongs to Speech-to-Text using remote streaming HTTP/SSE transport. Select FunASR when you need capabilities focused on speech-to-text and QuillHub when you require tools for speech-to-text.