Skip to main content

05 · MCP connectivity and services

MCP configuration tells a harness how to contact a tool. It does not install a service, prove authentication or execute inference. scripts/mcp-port-table.json is the full pack's declared connectivity source; configure-mcp-all-tools.sh merges the selected tool configuration.

ComponentDeclared transportShipped default
surreal-memorySSE/HTTP MCPhttp://localhost:23001/mcp/sse
prometheus-knowledgeHTTP MCPhttp://localhost:8942/mcp
ForgeHTTP JSON-RPChttp://localhost:8943/mcp
liter-llmstdio MCPliter-llm mcp --transport stdio --config <explicit-config>
sycophancy-correctionOn-demand stdioInstalled binary from the pinned skill package
sequential-thinkingOn-demand stdioConfigured npm MCP package
Tavily / FirecrawlOn-demand stdio adaptersConfigured package and environment credentials

These defaults are configuration observations, not a promise that all adapters exist in a session. The liter-llm MCP process needs an explicit config path; a configured gateway alias or successful model listing is not demonstrated inference. Optional hosted web adapters require their own credentials and policies.

Operations and scope​

Follow Services, ownership and recovery for source owners, platform templates, database identity, install/start/stop and backups. Native memory defaults to namespace/database memory/mcp; mini Compose uses memory/main_local_384. A matching port does not merge those stores.

Local KBD uses its signed runtime without a sync daemon. Connected control and replication belong to optional Companion through the integration contract; no Sovereign service is declared in the current MCP port table.

Memory recall, hook enqueueing, worker reconciliation and knowledge snapshots have separate paths. See Memory and Learning, team memory and hook lifecycle. Missing remote services can leave durable work pending; inspect the receipt rather than interpreting exit zero as delivery.

Previous: The Four-Layer Pipeline · Next: Memory and Learning.