TypeWhisper MCP
Connects to the TypeWhisper macOS app to let coding agents transcribe local files, inspect model status, search history, and manage dictionary terms and corrections.
README
TypeWhisper MCP
@typewhisper/mcp exposes the local TypeWhisper API as a Model Context Protocol server for coding agents and other MCP clients.
It connects to the TypeWhisper macOS app running on the same machine and lets agents transcribe local files, inspect model status, search transcription history, and manage Dictionary terms and corrections.
Requirements
- macOS with TypeWhisper installed
- TypeWhisper local API server enabled in
Settings > Advanced - Node.js 20 or newer
Install
npm install -g @typewhisper/mcp
For local development from this repo:
npm install
npm run build
node dist/bin.js --help
MCP Configuration
Most MCP clients can run the server over stdio:
{
"mcpServers": {
"typewhisper": {
"command": "npx",
"args": ["-y", "@typewhisper/mcp"]
}
}
}
For a local checkout:
{
"mcpServers": {
"typewhisper": {
"command": "node",
"args": ["/Users/marco/Projects/typewhisper-mcp/dist/bin.js"]
}
}
}
Discovery
By default, the server mirrors the TypeWhisper CLI discovery behavior:
TYPEWHISPER_API_BASE_URL,TYPEWHISPER_API_PORT, andTYPEWHISPER_API_TOKEN~/Library/Application Support/TypeWhisper/api-discovery.json~/Library/Application Support/TypeWhisper/api-porthttp://127.0.0.1:8978
Use --dev or TYPEWHISPER_DEV=1 to read TypeWhisper-Dev discovery files.
typewhisper-mcp --dev
typewhisper-mcp --base-url http://127.0.0.1:8978 --api-token "$TYPEWHISPER_API_TOKEN"
Tools
typewhisper_statustypewhisper_list_modelstypewhisper_transcribe_filetypewhisper_search_historytypewhisper_list_dictionary_termstypewhisper_upsert_dictionary_termstypewhisper_delete_dictionary_termtypewhisper_list_dictionary_correctionstypewhisper_upsert_dictionary_correctiontypewhisper_delete_dictionary_correction
typewhisper_transcribe_file requires an absolute file path because TypeWhisper runs as a separate macOS app process.
Recorder and live dictation controls are intentionally not part of the first release.
Development
npm run typecheck
npm test
npm run build
npm pack --dry-run
License
GPL-3.0-only
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.