Overview
Wednesday is an open-source MCP server that staffs small open models as a verified engineering team. You keep the client you already use; Wednesday gets a team.
What Wednesday is#
Wednesday turns a plain-language request into planned, verified engineering work. It connects to Claude Code, Codex, Cursor, OpenCode, Claude Desktop or any other MCP client over stdio. The host model does not do the work: it hands the request in, waits, and reports the verdict.
you -> "add a quantity input to the cart page"
client -> wednesday_run("add a quantity input to the cart page")
job accepted, id 3f9c..., workspace validated
client -> wednesday_wait(id)
working: planner, coder, verification...
client -> wednesday_result(id)
completed, tests PASS, files, receipt
Behind that one tool call is the whole team: a plan, engineering seats, a controlled sandbox, real verification commands, a capped repair loop, a review, and a receipt persisted on your machine.
Wednesday is not a model, a model host, or a training service. You bring the models — hosted with your own key, or local on your own hardware. Keys and state stay in ~/.wednesday/.
The invariant#
The outside model cannot call architect, coder, reviewer or any other seat. If it could, it would become the team lead and the small-model crew would become day labour — progress that destroys the point. The surface is coarse on purpose, and the server test asserts that no seat is exposed.
The seats are real engineering roles, not tool names. They plan, write, test, review, and audit inside Wednesday. The host model is a messenger.
What you need#
- Node.js 24 or newer on Windows, macOS or Linux.
- A model backend — your own OpenRouter or NVIDIA NIM key, or any local OpenAI-compatible server (Ollama, LM Studio, llama.cpp, vLLM).
- An MCP client — Claude Code, Codex, Cursor, OpenCode, Claude Desktop, or another client that can run a local stdio server.
No account, no hosted control plane, and no server of ours in the path.
What is real today#
Wednesday is shipped for its MCP scope. The honest state of the surface matters more than a feature list, so this page says what is shipped and what is still owed.
| Area | State |
|---|---|
| MCP server over stdio | Shipped. Protocol handshake, tools, prompt, progress notifications; tested end to end against a real stdio fixture. |
wednesday setup | Shipped. Registers five clients, backs up every file it touches, is idempotent, and leaves configs it cannot parse byte-for-byte alone. |
| Crew adoption | Shipped. The MCP server adopts the active crew at startup and reports in_sync: false when the disk changed underneath it. |
| One live run in a real host client | Still owed. The surface is proven against fixtures, not yet against a real host model doing a real hand-off. |
| HTTP transport | Not built. Stdio only, which is what desktop clients want first. |
| Approvals / MCP elicitation | Not built. Over MCP the team runs unattended inside its sandbox. |
| Job ids across a server restart | Not built. Jobs live in memory; task records and the event log survive on disk. |
| Parallel jobs | Deliberately not built. One job at a time: shared state home, shared workspace, one event stream. |
What Wednesday is not#
- Not a model. It has no weights and no inference of its own.
- Not a model host. A local server or a hosted provider serves the models; Wednesday routes to it.
- Not a training service. It does not fine-tune anything.
- Not a hosted control plane. There is no Wednesday server to send your code or keys to.
The product is the MCP server plus a small operator CLI. Everything else is the client you already use.
Where to go next#
If you want to run something now, start with the Quickstart. If you are deciding whether the design fits, read Crews & shapes and Verification. If something is already broken, Troubleshooting names the usual causes.