Servers
26
External and internal MCP endpoints in the host connection manager
Enterprise MCP Platform
AIOS MCP Host, Server, Gateway, and Registry
Architecture foundation for tenant-aware enterprise MCP orchestration with secure tool routing, policy enforcement, registry governance, and observability.
Modes: host, server, gateway, registryPipeline stages: 14Policy rules: Active
Tools
38
Tool registry entries with permissions and capability requirements
Resources
38
Resource registry entries across enterprise data classes
Prompts
15
Versioned prompts with approvals and release metadata
Gateway Monitor
Policy and context enriched orchestration pipeline
Every request is processed through authentication, tenant resolution, RBAC, role context, organization context, knowledge, memory, decision, workflow, routing, aggregation, and audit.
authenticationtenant-resolutionrbacrole-contextorganization-contextknowledge-graph
Total stages: 14 · Responsibilities: 9
Health Center
Connection and compatibility monitoring
Overall
warning
Avg latency
69 ms
Tool failures
11
Auth failures
1
MCP Registry
Installed server governance
26 installed server records with assignment, latency, error, update, and approval metadata.
Tool Registry
Permission-aware tool contracts
Every tool is typed with provider, server, role, permissions, capability requirements, schemas, and health state.
Resource Registry
Enterprise resource mapping
Documents, databases, knowledge, CRM, ERP, files, emails, reports, and dashboard resources are represented in one shared registry.
Prompt Registry
Versioned enterprise prompt governance
Prompt contracts include authoring metadata, approvals, change history, releases, and model or agent associations.
Observability
Execution, latency, and cost analytics
Requests: 0 · Success: 100% · Avg latency: 0 ms · Cost estimate: 0.03
Execution history events: 0
Foundation Scope
Prepared architecture surfaces
MCP Dashboard, Connection Manager, Registry, Health Center, Tool Explorer, Prompt Explorer, Resource Explorer, and Gateway Monitor are now represented through shared platform architecture and hooks.