You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 386dd54
Browse filesBrowse the repository at this point in the historyBrowse files
fix(harness): treat a blank MCP cursor as none and wait for connecting servers
- A blank cursor lists the first page; any other cursor goes back exactly as given.
- Resource tools wait for servers still connecting, so none is left out of a listing.
- Resource failures carry the server's own message; listings name the server beside it.
- Docs: where stdio servers start off a local sandbox, $NAME values, command caching,
sign-in, and retries after a failed connect.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: sites/www/content/docs/customize/mcp.mdx
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ CodeWork connects to [MCP](https://modelcontextprotocol.io) servers over stdio o
10
10
11
11
MCP servers always run on your machine, the one running CodeWork, whatever sandbox the session uses.
12
12
13
-
- A stdio server starts in the session's directory when the session runs in the local sandbox, otherwise in the project directory.
13
+
- A stdio server starts in the session's directory when the session runs in the local sandbox, otherwise in the session's folder on your machine.
14
14
- HTTP servers are called from your machine.
15
15
- Output too large to show, and binary files, are saved to your OS temp directory.
16
16
@@ -41,7 +41,9 @@ User servers go in `~/.codework/mcp.json`, project servers in `.codework/mcp.jso
41
41
|`url`, `headers`| HTTP | A streamable HTTP endpoint. SSE is not supported. |
42
42
|`enabled`, `timeout`, `exposure`, `toolExposure`| both | Off switch, per-request timeout in seconds (default 60), and which tools the model sees. |
43
43
44
-
`env` and `headers` values can use `${NAME}` for an environment variable, or `!command` to use a command's output.
44
+
`env` and `headers` values can use `${NAME}` or `$NAME` for an environment variable (`$$` for a literal `$`), or `!command` to use a command's output. A command runs once, and its output is reused until CodeWork restarts.
45
+
46
+
Servers that need you to sign in are not supported yet.
45
47
46
48
A broken file or entry is reported and skipped. The other servers still connect.
47
49
@@ -66,6 +68,6 @@ Servers with resources also add `list_mcp_resources`, `list_mcp_resource_templat
66
68
## Connections
67
69
68
70
- Servers connect in the background. A message waits up to 10 seconds for servers it starts whose tools the model sees: all of them at first, then new or changed ones.
69
-
- If a server stops, the next call starts it again.
71
+
- If a server stops, the next call starts it again. If it fails to connect, your next message tries again.
70
72
- Edits to `mcp.json` apply from your next message. Changing only `exposure` or `toolExposure` keeps the server running.
71
73
- Server log messages go to `~/.codework/mcp.log`.
0 commit comments