← Back to directory

Witsy

Community

Desktop AI assistant and universal MCP client for many model providers

GitHub source repository ↗

★ 2.0k Stars Category · Other Popular Source revision c81c7de417a6

45FMRS · D

Reliability

6/20

Security and permissions

8/20

Maintenance

11/20

Documentation

12/20

Setup experience

8/20

The source presents Witsy as a feature-rich desktop AI assistant and universal MCP client, not as a separately deployable MCP tool server. Its strengths are broad model-provider support, local models, desktop shortcuts, document retrieval, agents, and an HTTP API. Users should evaluate third-party data handling, API costs, local-file access, and MCP tool permissions before use.

Read the FMRS scoring method →

Witsy is an Electron desktop AI application and universal MCP client. It connects to cloud and local language models and supports running MCP servers. The README also lists document retrieval, speech transcription, image and video generation, agents, prompts, shortcuts, and a local HTTP API. No MCP server manifest or tool list is provided in the source, so this profile does not identify Witsy as a server exposing MCP tools.

Tools

The tool list has not been reviewed yet.

Setup

Download Witsy from GitHub Releases, or install it on macOS with brew install --cask witsy. To build from source, run npm ci and npm start. Cloud model providers require API keys configured in the application. Ollama requires a local Ollama installation and downloaded models.

Fit and risk

Best for

Desktop users who want one interface for many model providers
Users who want to run Ollama models locally
Users needing desktop shortcuts, document retrieval, or agent features
Developers integrating desktop AI actions through a localhost HTTP API

Not for

Users seeking a standalone MCP server that provides tools to other MCP clients
Users seeking a confirmed client-specific MCP server configuration
Users who do not want to configure cloud API keys or install a local model runtime

Required permissions

Cloud models, search, generation, and speech services require the relevant API keys
Ollama requires a local installation and model files
Local-file RAG and the local filesystem plugin require access to selected files
Prompt Anywhere, AI commands, and global shortcuts interact with other desktop applications
The local HTTP API listens on localhost port 8090 by default, or the next available port
CLI installation may require creating system-level symlinks on macOS or Linux

Risks and side effects

User-provided API keys are used with configured third-party services; costs and data handling depend on those providers
Local files, prompts, and conversations may be sent to the selected cloud models or services
The HTTP API is localhost-only by default; exposing it through a reverse proxy requires user-configured authentication
MCP servers, Python execution, agents, and local-file features can expand the actions or data accessible to the model
The software is licensed under AGPL-3.0

Troubleshooting

Confirm that Witsy is running and that the selected provider API key is valid
For Ollama, confirm that Ollama is installed, running, and has the required model downloaded
Check the actual HTTP API port; the README states 8090 for the desktop API but 4321 in the CLI section
For /api/complete, confirm that thread is an array of messages and set engine, model, and stream as needed
For MCP features, verify that the target MCP server is configured correctly; the source does not document a configuration format
For local-file RAG, confirm that a document repository exists and that OpenAI embeddings or an Ollama embedding model is configured

Use cases

Using multiple cloud and local language-model providers from one desktop application

Running MCP servers to extend model capabilities

Chatting with local files and documents through retrieval-augmented generation

Triggering prompts, AI commands, dictation, and read-aloud actions with shortcuts

Integrating the desktop assistant through its local HTTP API

Supported clients

Supported clients have not been confirmed yet.

Related MCP servers

Compare with other MCP servers