Other MCP Servers

Trailboss (cluster provisioning), Federal Compliance (NIST controls), and Tool Hub (aggregated discovery).

Trailboss

Trailboss is a single-tool MCP server for Kubernetes cluster provisioning. It orchestrates the creation and lifecycle management of workload clusters through the Frontier Management Cluster (FMC) using Cluster API (CAPI).

Property Value
Port 50059
Transport JSON-RPC at /jsonrpc
Namespace f3iai
Tools 1

Tools

Tool Description
trailboss_provision_cluster Provision a new Kubernetes workload cluster. Accepts cluster name, target infrastructure (AWS, bare-metal), node count, Kubernetes version, and instance type. Generates CAPI manifests, commits them to the GitOps repo, and triggers ArgoCD sync.

How It Works

Trailboss follows the GitOps provisioning pattern:

  1. Receives cluster specification from the LLM via trailboss_provision_cluster
  2. Renders CAPI manifests (Cluster, MachineDeployment, KubeadmControlPlane, etc.) from templates
  3. Commits the manifests to the Gitea repository under deploy/overlays/fmc/<cluster-name>/
  4. ArgoCD detects the new manifests and applies them to the management cluster
  5. CAPI controllers reconcile and create the workload cluster

Configuration

Environment Variable Description
GITEA_URL Gitea API URL for manifest commits
GITEA_TOKEN API token for repository access
GITEA_REPO Target repository (default: admin/federal-frontier-platform)

Federal Compliance

The Federal Compliance MCP Server provides 3 tools for querying NIST security controls and compliance status. It maps platform components to their applicable NIST 800-53 controls and reports on assessment status.

Property Value
Port 50053
Transport JSON-RPC at /jsonrpc
Namespace f3iai
Tools 3

Tools

Tool Description
compliance_list_controls List NIST 800-53 controls, optionally filtered by family (AC, AU, CM, IA, SC, etc.) or implementation status
compliance_get_control Get detailed information about a specific control, including description, implementation narrative, and assessment status
compliance_get_component_controls List all controls applicable to a platform component (e.g., Keycloak maps to IA controls, Ceph maps to SC controls)

Common Use Cases

  • “What IA controls apply to Keycloak?” — calls compliance_get_component_controls
  • “Show me all AC family controls” — calls compliance_list_controls with family filter
  • “What’s the status of AC-2?” — calls compliance_get_control

Data Source

Control definitions and implementation narratives are stored as structured data within the server. The mapping between platform components and NIST controls is maintained by the compliance team and updated through the standard deployment pipeline.

Tool Hub

The Tool Hub is a meta-server that provides aggregated tool discovery across all MCP servers. Instead of querying each server individually, clients can call Tool Hub to get a consolidated view of every tool available in the platform.

Property Value
Port 50058
Transport JSON-RPC at /jsonrpc
Namespace f3iai
Tools 1

Tools

Tool Description
toolhub_discover_tools Returns a unified manifest of all tools across all registered MCP servers, including server name, tool name, description, and input schema for each tool. Optionally filtered by server name or keyword search across tool descriptions.

How It Works

Tool Hub queries the mcp_servers table in PostgreSQL to get the list of registered servers, then calls tools/list on each server and merges the results into a single response. Results are cached with a configurable TTL (default 5 minutes) to avoid repeated upstream calls.

Use Cases

Tool Hub is primarily used by:

  • Compass API at startup for initial tool discovery
  • Administrative tooling to audit the full tool inventory
  • Monitoring to verify that all expected servers are responding and advertising their tools

Configuration

Environment Variable Description
DATABASE_URL PostgreSQL connection string for the mcp_servers table
TOOL_CACHE_TTL Cache duration in seconds (default: 300)