dottie-local
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@dottie-localsummarize the key points from this document"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
dottie-local
Local llama.cpp inference + optional dotbot harness.
Replaces local-ai-cli for LLM (ask + llm-server). Same CLI names on PATH after install. STT/TTS stays dottie-talk (transcribe / speak).
Same product shape as dottie-talk: HTTP + MCP + CLI. Talk is voice; this is tokens.
MIT. Public.
What it is
Layer | Role |
llama-server | Engine (GGUF → tokens). HTTP only. |
dottie-local | Façade: start/health, OpenAI proxy, MCP, CLI |
dotbot | Optional agent loop + |
Two processes. Never vendors Metal into the harness.
Related MCP server: MCP LLM Integration Server
Requirements
Node.js ≥ 22
llama-serveronPATHA GGUF (or let
-hfdownload). Default model:ggml-org/gemma-4-12B-it-GGUF(prefers cached Q8_0)
Install
git clone https://github.com/stevederico/dottie-local.git
cd dottie-local
npm install
npm link # puts ask, llm-server, dottie-local on PATHRemove or unlink old local-ai-cli ask / llm-server first so PATH does not shadow.
Quick start
ask "hello" # drop-in for local-ai-cli
echo "$(cat article.txt)" | ask "summarize this"
LLM_REASON=1 ask "prove it"
llm-server start|stop|restart|status|log
dottie-local agent "What tools do you have?" # harness + dot_* tools
dottie-local start # HTTP :1318
dottie-local healthUse with dottie-desktop
Point Settings Provider at Dottie Local (or set localBaseUrl). Base URL is the façade — not raw :8080:
http://127.0.0.1:1318 — needs llama-server on PATH + dottie-local start. Model list: GET /api/tags. Chat: POST /v1/chat/completions.
Ports
Port / env | Service |
8080 ( |
|
1318 ( | dottie-local HTTP façade (desktop stack; mac-use owns |
| enable thinking on |
| GGUF path or HF repo |
HTTP
Method | Path | Notes |
|
| Engine + façade |
|
| Ollama-shaped |
|
| Buffered |
|
| Dotbot harness → |
|
| Proxied to engine (SSE ok) |
|
| Proxied |
MCP tools
Tool | Does |
| One-shot chat, no tools |
| Dotbot loop with |
npm run mcpCLI
Command | Does |
| Stream completion (local-ai-cli drop-in) |
| Manage warm engine (local-ai-cli drop-in) |
| Same as |
| Dotbot tools |
| HTTP façade / status |
dottie-local stop only kills an engine this package spawned. llm-server stop also matches llama-server on the engine port (full drop-in).
Related
dottie-talk — local STT/TTS (replaces local-ai-cli
transcribe)local-ai-cli — predecessor; LLM half superseded here
dotbot — agent harness
llama.cpp — inference engine
dottie-desktop — desktop app
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
LLM Orchestration Agent (Mcp)
- QuallaaOAuthcom.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables seamless integration between Ollama's local LLM models and MCP-compatible applications, supporting model management and chat interactions.13758 npm171AGPL 3.0
- FlicenseBqualityDmaintenanceEnables integration of local LLM capabilities with MCP-compatible clients like Claude Desktop, Continue.dev, and Cline. Provides tools for processing text prompts through local language models using a customizable inference function.21-
- FlicenseCqualityDmaintenanceEnables MCP clients to interact with local LLMs via LM Studio, supporting dynamic chat, vision, RAG, file interaction, and model orchestration.28-
- AlicenseNot gradedqualityCmaintenanceExposes local LM Studio language models as MCP tools, enabling chat completions and model listing through a local OpenAI-compatible API without requiring API keys.MIT