What is the key difference between Speko and Contendeo?

Speko belongs to the Speech-to-Text category with local stdio execution, while Contendeo belongs to the Speech-to-Text category with cloud HTTP/SSE execution.

How do I install Speko or Contendeo 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 Speko and Contendeo free or paid?

Speko operates under a Free / Open Source model (No auth required). Contendeo operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Speko lists 0 tools with 0 views and 0 GitHub stars. Contendeo lists 4 tools with 0 views and 0 GitHub stars.

Can I use both Speko and Contendeo 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.

How do I install Speko or Contendeo in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Speko and Contendeo free to use, or do they require API keys?

Speko is listed under a Free / Open Source model with No auth required . Contendeo operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Speko and Contendeo at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both speko and contendeo as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Speko has a Quality Score of 40 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars. Contendeo holds a Quality Score of 47 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Speko vs Contendeo

In-depth architectural comparison of the Speko and Contendeo 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

Speko

Speech-to-Text · Local stdio

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

Contendeo

Speech-to-Text · Remote HTTP/SSE

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

Verdict Summary: Choose Speko if you need specialized Speech-to-Text tools running via a local process. Choose Contendeo 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 Speko 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 Speko Details

Choose Contendeo when:

You need dedicated capabilities in the Speech-to-Text domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: quick_transcribe, deep_analyze, clip_context.

Explore Contendeo Details

Feature & Specification Comparison

Specification	Speko Speech-to-Text	C Contendeo Speech-to-Text
Summary	Official Speko MCP server: build, run, and migrate voice agents (STT/TTS/V2V) for coding agents.	Multimodal video analysis MCP — transcription, vision, and OCR for any video URL.
Category & Scope	Speech-to-Text	Speech-to-Text
Quality signal

Tools & Capabilities Breakdown

Speko Tools (0)

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

Contendeo Tools (4)

quick_transcribe

Timestamped transcript with speaker identification. Audio-only. Fast.

deep_analyze

Full multimodal pipeline — transcript + keyframe vision + OCR, unified output.

clip_context

Analyze a specific timestamp range without paying for the full video.

batch_analyze

Process up to 10 videos in parallel with cross-video synthesis.

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

Speko Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "speko": {
      "command": "npx",
      "args": [
        "-y",
        "@spekoai/mcp@latest"
      ]
    }
  }
}

Contendeo Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "contendeo": {
      "url": "https://img.shields.io/badge/MCP-Compatible-00FF41?style=flat-square"
    }
  }
}

Frequently Asked Questions

Speko is categorized under Speech-to-Text and uses a local stdio subprocess. In contrast, Contendeo belongs to Speech-to-Text using remote streaming HTTP/SSE transport. Select Speko when you need capabilities focused on speech-to-text and Contendeo when you require tools for speech-to-text.

More alternatives to Speko More alternatives to Contendeo Speech-to-Text category hub Canonical compare URL

Related MCP Server Comparisons

Popular comparisons with Speko

Popular comparisons with Contendeo

Contendeo vs Whisper Windows Mcp