What is the key difference between FunASR and Vocce transcribe?

FunASR belongs to the Speech-to-Text category with local stdio execution, while Vocce transcribe belongs to the Speech-to-Text category with local stdio execution.

How do I install FunASR or Vocce transcribe in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are FunASR and Vocce transcribe free or paid?

FunASR operates under a Free / Open Source model (No auth required). Vocce transcribe operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

FunASR lists 0 tools with 0 views and 20,219 GitHub stars. Vocce transcribe lists 0 tools with 0 views and 0 GitHub stars.

Can I use both FunASR and Vocce transcribe together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

FunASR vs Vocce transcribe

In-depth architectural comparison of the FunASR and Vocce transcribe 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

Vocce transcribe

Speech-to-Text · Local stdio

Quality: 36/100 (Fair) | Auth: No auth required

Verdict Summary: Choose FunASR if you need specialized Speech-to-Text tools running via a local process. Choose Vocce transcribe if your workspace requires Speech-to-Text integration with local subprocess execution. 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).

Explore FunASR Details

Choose Vocce transcribe 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).

Explore Vocce transcribe Details

Feature & Specification Comparison

Specification	FunASR Speech-to-Text	Vocce transcribe Speech-to-Text
Summary	Transcribe local audio with FunASR and SenseVoice using private, on-device inference.	Transcribe audio/video to text + SRT/VTT via vocce's hosted Whisper. No API key required.
Category & Scope	Speech-to-Text	Speech-to-Text
Quality signal

Tools & Capabilities Breakdown

FunASR Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Vocce transcribe Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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 Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "funasr": {
      "command": "uvx",
      "args": [
        "torch"
      ]
    }
  }
}

Vocce transcribe Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vocce-transcribe": {
      "command": "npx",
      "args": [
        "-y",
        "vocce-transcribe-mcp"
      ]
    }
  }
}

Frequently Asked Questions

FunASR is categorized under Speech-to-Text and uses a local stdio subprocess. In contrast, Vocce transcribe belongs to Speech-to-Text using local stdio subprocess. Select FunASR when you need capabilities focused on speech-to-text and Vocce transcribe when you require tools for speech-to-text.

More alternatives to FunASR More alternatives to Vocce transcribe Speech-to-Text category hub