HN Showcase
Back to browse
Mcplexer.com

Mcplexer.com

by maxrev17·Jun 24, 2026·4 points·1 comment
Visit ProjectView on HN

AI Analysis

●●SolidBig BrainShip It

Unified MCP runtime across Claude, Cursor, and Grok with cross-harness delegation.

Strengths
  • •Cross-harness delegation lets strategic models assign inspection and testing tasks to worker models
  • •Directory-scoped routing determines which servers, tools, and approval policies are available per workspace
  • •Six months of daily dogfooding proves the system works in practice
Weaknesses
  • •UI has acknowledged rough edges that need polishing
  • •MCP coordination space is becoming increasingly crowded with similar tools
Category
AI/ML
Target Audience

AI developers building with multiple MCP clients and agent frameworks

Similar To

Continue · Cursor · Sourcegraph Cody

Post Description

Directory scoped workspaces, cross-harness and model delegation, inter-agent and machine mesh for messaging and coordination, brw - Claude chrome beating cross harness chrome control (can work remotely too,good for nomads!), mcp multiplexing (and batched code execution with dynamic context saving tool search), approvals, secret helper, skills registry (with context preserving dynamic loading).

Rough edges on the ui, daily driven for 6mo.

Similar Projects

Developer Tools●●Solid

CasperAI – A local MCP server for cross-platform engineering context

It stitches Slack threads, PRs, tickets and docs into a local "context lake" and can point a mention like handlePayment() straight to the file and related PRs — very practical for debugging and postmortems. The use of SQLite FTS5 for local full-text search plus MCP for a unified context layer is a smart, pragmatic combo; success will hinge on connector reliability and search/ranking quality, not the README.

Niche GemSolve My Problem
chose166
114mo ago
Developer Tools●●Solid

CasperAI – A local MCP server for cross-platform engineering context

It builds a local 'context lake' (SQLite + FTS5) that stitches Slack threads, PRs, tickets and docs to precise code locations so queries like "Why did the payment service deploy fail last week?" return linked commits, messages and files. The local-first approach is a sensible privacy + reliability choice and the bi-directional linking of mentions to file:line is the clearest practical win here. That said, the idea sits in a crowded space—quality of connectors and ranking will determine whether this is indispensable or just another repo-chat tool.

Niche GemShip It
chose166
104mo ago