---
name: "mcp-client-bridge-integration"
description: "Aggregate multiple MCP servers into a unified agent tool execution hub."
metadata:
  author: "Model Context Protocol"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "connect mcp client to multiple servers"
  - "list tools across mcp servers"
  - "route tool call to mcp server"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# Model Context Protocol Client Bridge & Multi-Server Hub

Builds custom MCP client applications using Client class: discovering tools across multiple remote servers, multiplexing namespaces, routing tool calls, and maintaining resource caches.

## When to Invoke
Invoke this skill whenever you need to:
- connect mcp client to multiple servers
- list tools across mcp servers
- route tool call to mcp server

## Execution SOP & Rules
1. Instantiate independent Client instances for each configured server endpoint.
2. Fetch tool lists concurrently with Promise.all([clientA.listTools(), clientB.listTools()]).
3. Route incoming tool call requests to the specific client owning the target capability.
4. Implement health checks and automatic reconnection for intermittent server disconnects.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.