Context Harness v0.2.0 ships with a native MCP Streamable HTTP endpoint, pre-built binaries for all major platforms, and updated docs across the board.

What changed

Native MCP protocol support. The server now exposes a /mcp endpoint that speaks the MCP Streamable HTTP transport — the same JSON-RPC-over-HTTP protocol that Cursor, Claude Desktop, and other MCP clients use natively.

Previously, connecting Cursor required either pointing it at the base URL (which only exposed REST endpoints) or using the command/args subprocess approach. Now it’s just a URL:

{
  "mcpServers": {
    "context-harness": {
      "url": "http://127.0.0.1:7331/mcp"
    }
  }
}

What’s exposed via MCP:

MCP MethodMaps to
tools/listAll registered tools (built-in + Lua + Rust)
tools/callExecute any tool by name
prompts/listAll registered agents as MCP prompts
prompts/getResolve an agent’s system prompt

The REST endpoints (/tools/list, /tools/{name}, /agents/*, /health) are still available for custom integrations.

Pre-built binaries

You no longer need Rust installed to use Context Harness. Every release now ships pre-compiled binaries for:

Download from GitHub Releases:

curl -L https://github.com/parallax-labs/context-harness/releases/latest/download/ctx-macos-aarch64.tar.gz | tar xz
sudo mv ctx /usr/local/bin/

SHA256 checksums are included for every archive.

Upgrading

If you have existing MCP client configs that use the old command/args approach or a bare http://localhost:7331 URL, update them to point to http://127.0.0.1:7331/mcp.

Start the server separately:

ctx serve mcp --config ./config/ctx.toml

Then update your .cursor/mcp.json, Claude Desktop config, or any other MCP client to use the new URL.

What’s next