wednesday docs
Docs/Getting started

Install & connect

Wednesday is a source checkout with two binaries and a small CLI. There is no installer app, no hosted account, and no daemon to keep running.

Requirements#

RequirementDetail
Node.js24 or newer on Windows, macOS or Linux.
Model backendAny OpenAI-compatible chat endpoint. Local servers need no key; hosted providers use your own.
MCP clientClaude Code, Claude Desktop, Codex, Cursor, OpenCode, or another local stdio client.
DiskThe checkout plus ~/.wednesday/ for config, crews, skills and run state.

Wednesday does not require a GPU. The model server may be on the same machine, on another machine on your network, or behind a tunnel URL.

Install from source#

macOS / Linux
git clone https://github.com/lab1207/Wednesday.git
cd Wednesday
./install.sh
Windows (PowerShell)
git clone https://github.com/lab1207/Wednesday.git
cd Wednesday
npm install
npm link

npm link creates the wednesday and wednesday-mcp commands. If you prefer not to link globally, wednesday setup still registers an absolute node <checkout>/bin/wednesday-mcp.js command; the CLI itself can be run with node bin/wednesday.js.

Register with your client#

wednesday setup is the supported path. It detects a client from its config file, its directory, or its binary on PATH, then registers Wednesday through the client’s own command where one exists.

FlagWhat it does
noneRegister every client found on this machine.
--dry-runPrint the plan; write nothing.
--allAlso create configs for clients that are not installed.
--client <id>Register one client. Repeatable or comma-separated.
--command "<line>"Register a different command (for example a globally linked wednesday-mcp).
--jsonPrint the result array for scripts.
plan, then write
wednesday setup --dry-run
wednesday setup
wednesday setup --client cursor
wednesday setup --client claude,codex

What setup actually writes#

  • An absolute command. node <checkout>/bin/wednesday-mcp.js. A bare wednesday-mcp needs a global link and, on Windows, depends on how a client spawns a .cmd shim. The absolute form has neither dependency.
  • A backup first. Every touched file becomes <file>.wednesday-backup-<timestamp> before the write.
  • Only its own keys. The root object and every other key survive. In ~/.codex/config.toml it replaces only the command/arguments keys inside [mcp_servers.wednesday]; your own keys in that table stay where they are.
  • Strict JSON or skip. A config with comments or a syntax error is reported as skipped and left byte-for-byte alone. Use the client’s own mcp add command for that file.
  • Idempotent. A registered server reports unchanged and no second backup is written.
  • OpenCode V2 shape only. mcp.servers.<name>, never mcp.<name>.

Manual registration#

If you prefer to wire a client by hand, these are the shapes Wednesday writes.

Claude Code

Claude Code
claude mcp add wednesday -- wednesday-mcp
# add --scope user to make it available in every project

OpenCode

opencode.jsonc
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "wednesday": {
        "type": "local",
        "command": ["wednesday-mcp"]
      }
    }
  }
}

Claude Desktop / Cursor

mcpServers
{
  "mcpServers": {
    "wednesday": {
      "command": "wednesday-mcp"
    }
  }
}

Codex CLI

~/.codex/config.toml
[mcp_servers.wednesday]
command = "wednesday-mcp"

Scope and limits#

  • No uninstall verb. wednesday setup --remove does not exist. Removing a line from someone’s config is a different risk class and needs its own design.
  • Global scope only. Project-scope registration (./.mcp.json, .cursor/mcp.json, ./opencode.json) is not built. Global is what makes “install once” true.
  • Five clients. Claude Code, Claude Desktop, Codex, Cursor, OpenCode. VS Code, JetBrains and Zed are not covered yet.
  • The checkout is pinned. Moving the directory means rerunning wednesday setup. The receipt says so.

Verify the connection#

  1. Restart the client, or reconnect its MCP server list. The server starts on demand; it is not a background daemon.
  2. Confirm the crew is readable: wednesday team show.
  3. Ask the client to call wednesday_team. It is read-only and returns the crew plus in_sync.
  4. If the server is missing, see Troubleshooting before editing config by hand.