talkito

TalkiTo (Talkito) can act as an MCP server that lets you access its capabilities remotely. Run the server locally with the CLI flag to start the MCP server endpoint, after which you can interact with its tooling and configurations via standard MCP client requests. The Talkito MCP server exposes the built-in command surface of the Talkito CLI, enabling remote control of Claude Code, Codex, and related features for automated workflows. Typical use cases include integrating Talkito into orchestration scripts, triggering claude/codex-based actions from CI, or using it as a backend for extensions that need programmatic access to Talkito’s TTS/ASR and agent compatibility features.

Prerequisites:

• Python 3.8+ and pip
• git (optional, for cloning)

Install from source (stable):

# Clone the repository
git clone https://github.com/robdmac/talkito.git
cd talkito

# Create and activate virtual environment (recommended)
python3 -m venv venv
source venv/bin/activate

# Install dependencies
pip install .

Run the MCP server:

talkito --mcp-server

If you prefer to install via the One-liner (if provided by the project), use the recommended script as described in the README:

curl -sSL https://raw.githubusercontent.com/robdmac/talkito/main/install.sh | bash

Prerequisites for end-user usage (optional):

• macOS: install PortAudio for full TTS/ASR functionality (brew install portaudio)
• Ensure network access for remote MCP interactions if you plan to expose the server externally

Validation:

• After starting, confirm the MCP endpoint is reachable and test a simple command like listing available actions or invoking a sample command through your MCP client.

Notes and tips:

• Talkito supports multiple TTS/ASR providers; configure credentials and preferences as environment variables or via runtime options when using the MCP server.
• When running in MCP mode, you can drive Talkito commands programmatically (e.g., claude, codex) from your orchestrator or extension.
• If you encounter audio device issues for TTS/ASR in a headless environment, consider using a cloud or offline provider as appropriate and verify that the required dependencies are installed.
• For web extension usage or remote triggers, you can start the MCP server in the background and connect to it from other processes or services.
• Ensure your environment variables for provider keys (e.g., AWS, Azure, Google) are set before making requests that require them.