MCP Servers Overview

Benchmarked against: Anthropic — MCP in the API / MCP connector Protocol: Model Context Protocol (MCP) — open standard Architecture: Multiple concurrent MCP servers per agent session

SuperPortia agents connect to multiple MCP servers simultaneously. Each server exposes a set of tools for a specific domain — knowledge management, infrastructure, database operations, browser automation, and more. This page describes the server architecture and how they fit together.

---

Server architecture

All servers run concurrently. The agent chooses which tool to call based on the task at hand — the MCP protocol handles routing to the correct server.

---

Server catalog

Server	Type	Transport	Tools	Purpose
Local UBI	Custom	stdio	~30	Knowledge base, WO system, dispatch, file ops, intel
Cloud UB	Custom	HTTP	~20	Cloud knowledge base, WO system, messaging, fleet ops
Cloudflare	Official	HTTP	2	Infrastructure API search + execute
Supabase	Official	HTTP	~25	Database management, migrations, edge functions
Chrome	Extension	WebSocket	~15	Browser automation, screenshots, page interaction
Claude Preview	Built-in	stdio	~15	Dev server management, preview, testing
Memory	Built-in	stdio	~8	Knowledge graph (entities, relations, observations)
Filesystem	Built-in	stdio	~10	File system read/write/search

---

Custom vs official servers

Custom servers (built by SuperPortia)

Server	Codebase	Maintained by
Local UBI	ub/ directory — Python MCP server	Engineering team
Cloud UB	ss3-cloud-ub/ — Cloudflare Worker (TypeScript)	Engineering team

These are the core servers that implement SuperPortia-specific functionality: the Universal Brain, Work Order system, Agent Messaging, Intelligence Operations, and Dispatch Engine.

Official servers (third-party)

Server	Provider	Configuration
Cloudflare	Cloudflare	API token in MCP config
Supabase	Supabase	Project ref + API key in MCP config
Chrome	Claude in Chrome extension	Browser extension
Claude Preview	Claude Code	Built into Claude Code
Memory	Claude Code	Knowledge graph MCP
Filesystem	Claude Code	Filesystem access MCP

Official servers are configured in the Claude Code MCP settings and used as-is. They provide infrastructure access without custom code.

---

Server deployment model

Layer	Servers	Shared?
Per-ship	Local UBI, Chrome, Preview, Memory, Filesystem	No — each ship runs its own
Cloud (shared)	Cloud UB, Cloudflare, Supabase	Yes — all ships connect to same instance

This architecture means:

• Local UBI has access to the ship's filesystem (for file ops, code search, local dispatch)
• Cloud UB is the single source of truth for knowledge, work orders, and messaging
• Both expose similar UB tools — the agent uses Cloud UB for cross-ship data, Local UBI for ship-specific operations

---

Configuration

MCP servers are configured in the Claude Code settings file. Each server definition includes:

{
  "mcpServers": {
    "server-name": {
      "command": "python",
      "args": ["-m", "ub.mcp_server"],
      "env": {
        "SP_SHIP_ID": "SS1",
        "SP_AGENT_ID": "Mac CLI 小克"
      }
    }
  }
}

Field	Purpose
command	Executable to start the server
args	Command-line arguments
env	Environment variables (ship ID, agent ID, API keys)

For HTTP-based servers (Cloud UB, Cloudflare, Supabase), configuration includes the remote URL and authentication tokens.

---

Tool naming convention

When multiple servers expose tools, the full tool name includes the server identifier:

mcp__{server-id}__{tool-name}

Examples:

• mcp__ubi__search_brain — Local UBI's search
• mcp__ss3-cloud-ub__search_brain — Cloud UB's search
• mcp__5595db01-...__search_brain — Local UBI (by UUID)

The agent sees all tools from all servers and chooses based on context.

---

Related pages

Page	Relationship
MCP Tools Overview	Complete tool catalog across all servers
How to Add an MCP Tool	Adding tools to existing servers
Cloud UB MCP	Cloud knowledge base server
Local UBI MCP	Ship-local MCP server
UB Governance	Rules governing UB operations