How dsk-dev-ai/mcp-nexus works
MCP Nexus is an MCP tool discovery, routing, and safe-execution gateway. An MCP client connects through stdio or Streamable HTTP; the server exposes registry, discovery, routing, approval, and invocation operations. Routing selects a registered tool, policy checks its permission scopes, and approved calls execute over local/stdio, Docker, or HTTP transports. The repository also provides operator CLI and dashboard interfaces, activity logging, and optional LLM routing. Some links reflect README or SOURCE INDEX references because implementation excerpts are partial.
Main entry points: server/server.ts MCP server · dashboard/server.ts Dashboard API · cli.ts Operator CLI · registry.ts Tool registry
Components 21
Gateway & operations
- MCP server
src/server/server.ts - HTTP gateway
src/server/httpGateway.ts - Operator CLI
src/cli.ts - Dashboard API
src/dashboard/server.ts - Configuration
src/config.ts
Tool catalog
- Tool manifests
src/registry/manifest.ts - Tool registry
src/registry/registry.ts
Discovery & routing
- Router coordinator
src/router/index.ts - Heuristic router
src/router/heuristic.ts - Intent overlay
src/router/intents.ts - Semantic router
src/router/semantic.ts - LLM router
src/router/llm.ts
Policy & execution
- Policy engine
src/policy/policy.ts - Permission scopes
src/policy/scopes.ts - Approval store
src/policy/approvals.ts - Tool executor
src/executor/executor.ts
Operations & plugins
- Activity log
src/telemetry/logger.ts - Plugin interfaces
src/sdk/interfaces.ts - Router benchmark
src/bench/suite.ts
Other components
- MCP client
- MCP tools
Connections 34
- MCP client → MCP server: connects stdio
README.md - MCP client → HTTP gateway: connects HTTP
README.md - HTTP gateway → MCP server: uses server
src/server/httpGateway.ts - Operator CLI → Configuration: loads settings
src/cli.ts - Operator CLI → Tool registry: manages tools
src/cli.ts - Operator CLI → HTTP gateway: starts gateway
src/cli.ts - Operator CLI → Dashboard API: starts dashboard
src/cli.ts - Operator CLI → Router benchmark: runs benchmark
src/cli.ts - Operator CLI → Tool manifests: parses manifests
src/cli.ts - MCP server → Tool registry: reads and updates
src/server/server.ts - MCP server → Router coordinator: routes requests
src/server/server.ts - MCP server → Policy engine: checks permissions
src/server/server.ts - MCP server → Permission scopes: derives scopes
src/server/server.ts - MCP server → Approval store: requests approval
src/server/server.ts - MCP server → Tool executor: executes calls
src/server/server.ts - MCP server → Activity log: records activity
src/server/server.ts - Tool manifests → Tool registry: validates entries
src/registry/registry.ts - Router coordinator → Heuristic router: tries provider
README.md - Router coordinator → Semantic router: falls back
README.md - Router coordinator → LLM router: optional fallback
README.md - Heuristic router → Intent overlay: matches intent
src/router/heuristic.ts - Heuristic router → Tool registry: scores tools
src/router/heuristic.ts - Semantic router → Tool registry: scores tools
src/router/semantic.ts - Dashboard API → Tool registry: serves tool data
src/dashboard/server.ts - Dashboard API → Router coordinator: routes queries
src/dashboard/server.ts - Dashboard API → Approval store: resolves requests
src/dashboard/server.ts - Dashboard API → Policy engine: manages policy
src/dashboard/server.ts - Dashboard API → Tool executor: uses executor
src/dashboard/server.ts - Dashboard API → Activity log: shows activity
src/dashboard/server.ts - Policy engine → Approval store: checks grants
src/policy/policy.ts - Tool executor → MCP tools: executes transport
README.md - Plugin interfaces → Tool registry: defines plugin contract
src/sdk/interfaces.ts - Plugin interfaces → Tool executor: defines plugin contract
src/sdk/interfaces.ts - Plugin interfaces → Policy engine: defines plugin contract
src/sdk/interfaces.ts