Quark

Why MCP doesn’t scale

MCP is JSON-RPC from the 2010s stretched over AI. Fine for desktop apps. In production it cracks.

What Quark fixes

A WebSocket channel stays alive. Streams. Server-side composition. Each call described in JSON Schema. Capability grants. All backward-compatible with MCP.

Code: MCP vs Quark

// 1. List repos
const repos = await mcp.call(
  'github.list_repos',
  { owner: 'anthropic' }
)

// 2. Filter client-side
const big = repos.filter(r => r.stars > 100)

// 3. Get names
const names = big.map(r => r.name)

// 4. Send to slack
await mcp.call('slack.notify', {
  channel: '#dev',
  items: names
})

await ch.pipeline([
  { tool: 'github.list_repos',
    input: { owner: 'anthropic' } },
  { filter: 'stars > 100' },
  { map: ['name'] },
  { tool: 'slack.notify',
    input_bind: {
      items: '$prev',
      channel: '#dev'
    } },
])

Live demo

Live in your browser. Click buttons — they hit the live Quark server at unyly.org/quark via WebSocket.