Frenchie vs Spoken

In-depth architectural comparison of the Frenchie and Spoken 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.

Which MCP Server Should You Choose?

Choose Frenchie 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 Frenchie Details

Choose Spoken when:

• You need dedicated capabilities in the Speech-to-Text domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Paid Service).
• You have access to required keys: SPOKEN_API_KEY.
• Primary tools included: Returns transcripts with real speaker names, not generic labels, Outputs clean Markdown with timestamps for easy parsing, Supports search by text query or Spotify/YouTube URL.

Explore Spoken Details

Feature & Specification Comparison

Specification	Frenchie Speech-to-Text	Spoken spokenmd Speech-to-Text
Summary
Category & Scope	Speech-to-Text	Speech-to-Text
Quality signal

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "frenchie": {
      "command": "npx",
      "args": [
        "-y",
        "@lab94/frenchie"
      ]
    }
  }
}

{
  "mcpServers": {
    "spokenmd-spoken": {
      "command": "npx",
      "args": [
        "-y",
        "spoken-mcp"
      ],
      "env": {
        "SPOKEN_API_KEY": "YOUR_SPOKEN_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons