Let a Server Component render a client Context directly to provide a value to descendants.
<div class="scene"><div class="node server" id="server">SERVER <b>theme: mint</b></div><div class="connector"><i id="token"></i></div><div class="node context" id="context"><ThemeContext value></div><div class="connector"><i id="token2"></i></div><div class="node client" id="client">CLIENT CHILD <b id="received">waiting</b></div></div>.scene{width:min(94vw,800px);height:min(86vh,320px);position:relative;overflow:hidden;display:flex;flex-direction:column;justify-content:space-between;border:1px solid var(--line);border-radius:14px;background:var(--surface);padding:clamp(9px,2.4vmin,20px);font:500 clamp(15px,4vmin,18px)/1.3 var(--font-sans,-apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif)}.scene b,.scene strong{font-weight:700}.label{color:var(--muted)}.code{font-family:ui-monospace,SFMono-Regular,Consolas,monospace}.pill{border:1px solid var(--line);border-radius:8px;padding:.4em .65em;background:var(--bg)}.active{border-color:var(--accent)!important;color:var(--accent)!important;background:color-mix(in srgb,var(--accent) 10%,var(--surface))!important}.scene{justify-content:center;gap:0}.node{width:100%;border:1px solid var(--line);border-radius:8px;padding:clamp(5px,2vmin,9px);display:flex;justify-content:space-between;gap:5px;align-items:center;font:700 clamp(12px,3vmin,15px) ui-monospace,monospace;min-height:clamp(32px,12vmin,46px)}.node b{color:var(--accent)}.node.on{border-color:var(--accent);background:color-mix(in srgb,var(--accent) 12%,var(--surface))}.context{text-align:center;justify-content:center}.connector{height:clamp(8px,2.4vmin,16px);display:flex;justify-content:center;position:relative}.connector:before{content:"";height:100%;border-left:2px solid var(--line)}.connector i{position:absolute;top:0;width:8px;height:8px;border-radius:50%;background:var(--accent);opacity:0}.connector i.run{opacity:1;animation:down .6s linear forwards}@keyframes down{to{top:100%}}let step=0;function tick(){step=(step+1)%4;for(const id of ["server","context","client"])document.getElementById(id).classList.remove("on");document.getElementById("token").classList.remove("run");document.getElementById("token2").classList.remove("run");document.getElementById("received").textContent=step===3?"theme: mint":"waiting";if(step===0)document.getElementById("server").classList.add("on");if(step===1){document.getElementById("context").classList.add("on");void document.getElementById("token").offsetWidth;document.getElementById("token").classList.add("run")}if(step===2){document.getElementById("context").classList.add("on");void document.getElementById("token2").offsetWidth;document.getElementById("token2").classList.add("run")}if(step===3)document.getElementById("client").classList.add("on")}tick();setInterval(tick,800)React 19.3 lets a Server Component import a Context created in a client module and render <Context value={...}> directly. This removes a client Provider wrapper that only forwarded the value.
The demo shows a server-read preference flowing through Context to a client descendant. It does not mean a Server Component can create Context or read it with useContext.
Use it when server-read settings should be provided to multiple client descendants through Context.