A
licenseNot graded
qualityD
maintenanceEnables AI assistants to have voice conversations and screen sharing capabilities via WebRTC, using Pipecat for speech-to-text and text-to-speech.
BSD 2-Clause "Simplified"
Jarvis MCP
by shantur
Related Servers
Alternatives to Jarvis MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to speak with realistic cloned voices via ElevenLabs TTS on Cloudflare Workers, supporting 29 languages and inline audio playback on both desktop and mobile.35 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to place real phone calls, engage in spoken conversations across 12 languages, and report the outcomes for tasks like booking appointments, answering questions, negotiating, or confirming orders.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to perform intelligent browser automation with session-based context analysis, including navigation, form filling, and content extraction through natural language.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI to control 3D VRM models via natural language, supporting expressions, animations, and bone manipulation in real-time through a web browser.-
- AlicenseAqualityDmaintenanceEnables continuous voice conversation with AI coding assistants by locally transcribing speech with Whisper and delivering utterances as text prompts.41MIT
TDQS
A3.7/5.0
Scored across 5 tools
Disambiguation4/5
Most tools have distinct purposes, though speak and converse overlap (converse includes speaking plus waiting for input). voice_status and get_voice_input are related but clearly different in scope. Descriptions help resolve ambiguity.
Naming Consistency3/5
Tool names mix single-word verbs (speak, converse) with noun-based names (voice_status) and verb_noun phrases (get_voice_input, end_conversation). No consistent pattern, but the naming remains readable and intuitive.
Tool Count5/5
Five tools is a well-scoped set for a voice interaction server. Each tool serves a clear function in the conversation lifecycle without unnecessary bloat.
Completeness4/5
The core voice lifecycle is covered: speaking, receiving input, full conversation, and ending. Minor gaps exist, such as not having a dedicated 'listen only' tool or explicit browser start control, but the automatic startup and status check mitigate these.
Maintenance
ActivityInactive
ResponsivenessNo issues