MCP Infrastructure

MCP Infrastructure

The Model Context Protocol (MCP) infrastructure is the inter-process communication layer that connects FoundUps agents, DAEs, and external tools. MCP enables agents to access capabilities across process boundaries — file systems, databases, browser automation, code analysis, and external APIs — through a standardized protocol.

The FoundUps ecosystem maintains multiple MCP components across different architectural layers.

---

Components

foundups-mcp-p1 (Top-level)

foundups-mcp-p1/ — The Phase 1 private MCP bridge. This is the primary MCP server implementation that provides the FoundUps-specific tool surface to agents. See the FoundUps MCP Bridge wiki page for the v1.4 perception schematic.

MCP Daemon

modules/infrastructure/mcp_daemon/ — The persistent MCP process manager. Keeps MCP servers running, handles lifecycle (start/stop/restart), monitors health, and routes connections between agents and tool servers.

MCP Manager

modules/infrastructure/mcp_manager/ — Configuration and orchestration layer for MCP server instances. Manages which MCP servers are active, their configuration, and routing tables.

Chrome DevTools MCP

mcp_servers/chrome_devtools_mcp/ — MCP server that exposes Chrome DevTools Protocol capabilities. Enables agents to interact with browser instances for web automation, page inspection, and JavaScript execution.

PAVS MCP

modules/infrastructure/pavs_mcp/ — MCP server for PAVS (Peer Autonomous Venture System) treasury operations. Provides treasury query, balance checking, and economic model access through MCP.

Secrets MCP

modules/infrastructure/secrets_mcp/ — Secure secrets management through MCP. Agents request credentials and API keys through this server rather than accessing them directly, maintaining security boundaries.

PQN MCP

modules/ai_intelligence/pqn_mcp/ — MCP server for PQN (Persistent Quantum Narratives) research operations.

Architecture

Agent (Hermes / OpenClaw / DAE)
    ↓
MCP Manager (configuration, routing)
    ↓
MCP Daemon (lifecycle, health)
    ↓
┌──────────────┬──────────────┬──────────────┐
│FoundUps MCP  │Chrome DevTools│  PAVS MCP   │
│  Bridge P1   │    MCP       │             │
├──────────────┼──────────────┼──────────────┤
│ Secrets MCP  │  PQN MCP     │  (future)   │
└──────────────┴──────────────┴──────────────┘

The MCP infrastructure follows the WSP 3 domain organization — MCP daemon and manager live in infrastructure/, domain-specific MCP servers live in their functional domains (ai_intelligence/ for PQN, infrastructure/ for PAVS and secrets).

Configuration

MCP server configuration is managed through .mcp.json at the repository root. This file defines which MCP servers are available, their startup commands, and connection parameters.

WSP Dependencies

• WSP 103 — FoundUp Federation Protocol: MCP access provisioning for cross-FoundUp communication
• WSP 106 — FoundUp API Gateway: MCP bridge referenced by gateway endpoints

---

Related Pages

• FoundUps MCP Bridge — v1.4 perception schematic for the primary MCP bridge
• FoundUps API Gateway — API gateway that provisions MCP access
• Hermes Agent — Builder agent that uses MCP for tool access
• DAE Architecture — DAEs communicate through MCP
• HoloIndex — Code intelligence accessible via MCP

---

Back to Wiki Home