jcode 0.96 brings remote MCP servers and OAuth into its coding agent
The standalone terminal agent can connect to HTTP and SSE tool servers, with explicit sign-in and a deadline for stalled handshakes.
Remote tools without a local server process
jcode 0.96.0 adds connections to remote Model Context Protocol servers over HTTP or SSE, according to its October 14 release notes. For users of the standalone coding-agent harness, that opens a documented route to hosted tool servers alongside existing local stdio integrations. This updates the agent’s tool connections, rather than introducing a language model or a plugin for another harness.
The versioned remote-MCP guide supports Streamable HTTP and legacy SSE. Users configure a server URL in ~/.jcode/mcp.json or a project’s .mcp.json, then manage connections with commands including jcode mcp list, test NAME and login NAME. The test command initializes the connection and lists tools before shutting down; it does not call an LLM or execute remote tools.
Sign-in is an explicit step
For compatible servers, jcode mcp login NAME opens an OAuth flow with PKCE and a loopback callback. Ordinary startup does not automatically launch interactive login. Servers without supported dynamic client registration can instead use a configured authorization header. The guide allows environment-variable references in headers, and stores OAuth credentials in a restricted-permission file under the jcode home directory.
Remote handshakes have a total 30-second deadline, separate from the timeout for individual tool calls. The documented schema cache and background connection process let responsive servers become available while slower connections continue. These are implementation descriptions, not an independently measured guarantee about every server’s startup time.
Install the harness, configure provider access
The MIT-licensed project documents Homebrew installation through brew tap 1jehuang/jcode followed by brew install jcode; existing installations can use jcode update. The release lists downloads for macOS, Linux, Windows and FreeBSD. Model-provider credentials and usage costs remain separate from remote-server authentication and installation of the harness.
There is a material packaging detail: the release says its binaries combine the existing 0.96.0 tag with a reviewed Windows listener repair. They are patched tag source, not the exact unchanged tagged tree, with hashes recorded in release-provenance.json. AITrending read the English release and versioned guides but has not run the packaged binaries or independently tested OAuth interoperability.