I've been building t2t, a voice-to-text app that works system-wide with a twist: it supports MCP (Model Context Protocol) servers for extensible automation.

*What it does:* - Hold `fn` → speak → text appears anywhere (local Whisper transcription) - Hold `fn+ctrl` → agent mode that connects to any MCP server - All processing is local except OpenRouter API calls for agent mode - Cross-platform: macOS, Windows, Linux

*Why I built it:* I wanted voice-to-text that wasn't tied to a specific app, and I got excited about MCP as a way to make the agent mode extensible. Instead of hardcoding integrations, you can connect to any MCP server (databases, APIs, file systems, etc.).

*Architecture:* - Rust + Tauri for the desktop app - Local Whisper model (whisper-rs) for transcription - Local MCP client (stdio/HTTP/SSE) - no remote workers - OpenRouter API for AI (direct calls from Rust) - Svelte 5 frontend

The MCP client runs entirely in Rust, so it works in both dev and production builds. Tool execution happens locally via JSON-RPC.

*Open source:* https://github.com/acoyfellow/t2t

I'd love feedback on the architecture, especially the local MCP client approach. Also curious if others find the MCP integration useful or if I'm overcomplicating things.

What do you think?