SpeechWeave vs Filesystem

A side-by-side look at the SpeechWeave and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

SpeechWeave logoSpeechWeaveSpeech-to-Text · Local subprocess (stdio)Transcribe local files and URLs with SpeechWeave's OpenAI-compatible API.59GoodAuth: not declaredFilesystem logoFilesystemFile Systems · Local subprocess (stdio)Secure file operations with configurable access controls.85ExcellentAuth: no auth required

Verdict: choose SpeechWeave for speech-to-text work as a local process; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

SpeechWeave logoChoose SpeechWeave when

  • You need dedicated capabilities in the Speech-to-Text domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like transcribe_file, transcribe_url, start_job_file.
Explore SpeechWeave

Filesystem logoChoose Filesystem when

  • You need dedicated capabilities in the File Systems domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like path, head, tail.
Explore Filesystem

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSpeechWeave logoSpeechWeaveFilesystem logoFilesystem
CategorySpeech-to-TextFile Systems
Quality signal59/100 · Good85/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars091,540
Directory activity 1 views 0 installs 0 upvotes 11 views 0 installs 0 upvotes
Tools817

Tools & capabilities

SpeechWeave tools 8

  • transcribe_fileUpload a local audio/video file and wait until transcription finishes. Prefer for short/medium clips when you need the transcript in this turn. Pass an absolute filesystem path (never raw binary). Set task='translate' to get an English translation instead of a same-language transcript. On wait timeout, returns job_id, then call get_job_status. For long audio you plan to poll yourself, use start_job_file instead.
  • transcribe_urlStart transcription from a public HTTPS URL and wait until it finishes. Prefer for short/medium media when you need the transcript in this turn. Set task='translate' to get an English translation instead of a same-language transcript. On wait timeout, returns job_id, then call get_job_status. For long audio you plan to poll yourself, use start_job_url instead.
  • start_job_fileUpload a local audio/video file and return a job id immediately without waiting. Use for long recordings or when you will poll later with get_job_status. Pass an absolute filesystem path. Set task='translate' for an English translation instead of a same-language transcript.
  • start_job_urlCreate a transcription job from a public HTTPS URL and return a job id immediately. Use for long media or deferred workflows; poll with get_job_status until completed, failed, or cancelled. Set task='translate' for an English translation instead of a same-language transcript.
  • get_job_statusFetch the current status of a transcription job (and transcript when completed). Poll until status is completed, failed, or cancelled. Pass response_format ('srt', 'vtt', or 'verbose_json') on a completed job to fetch it re-formatted.
  • cancel_jobCancel a queued or processing transcription job. Fails if the job is already terminal.
  • get_limitsFetch upload size ceilings for the calling API key (GET /v1/limits). Returns max_input_bytes, sync_max_bytes, and proxy_max_bytes plus MB equivalents. Call before transcribe_file or start_job_file when file size is large.
  • fetch_docReturn public SpeechWeave documentation for a slug. Use slug 'list' for the catalog. Bundled pages include quickstart, mcp, models, billing, and data_retention. Use slug 'api' for a live OpenAPI overview, or 'api/<operation_slug>' for one endpoint (e.g. api/get_v1_limits).

Filesystem tools 17

  • path
  • head
  • tail
  • paths
  • content
  • edits
  • oldText
  • newText
  • dryRun
  • sortBy
  • source
  • destination
  • +5 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

SpeechWeave

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "speechweave": {
      "command": "npx",
      "args": [
        "-y",
        "@speechweave/mcp"
      ]
    }
  }
}

Filesystem

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem"
      ]
    }
  }
}

Frequently asked questions

SpeechWeave is categorized under Speech-to-Text and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick SpeechWeave for speech-to-text work and Filesystem for file systems.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

SpeechWeave has no declared pricing — check the project's own site. Filesystem is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add speechweave and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, SpeechWeave has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Filesystem has 85/100 (Excellent) with 11 views, 0 installs and 91,540 GitHub stars.