Does Prototype offer persistent storage for its catalog data?

Yes, Prototype utilizes an SQLite database for persistent storage of its catalog data. It also includes automatic recovery mechanisms to ensure data integrity even after restarts.

How does Prototype ensure high availability and scalability?

Prototype is Kubernetes-ready, supporting 3+ replicas with pod anti-affinity for high availability and Horizontal Pod Autoscaling (HPA) for CPU/memory-based scalability to handle varying loads.

What is Prototype and its primary purpose?

Prototype is a centralized catalog server designed to track domain-specific Model-Controller-Provider (MCP) servers and efficiently route incoming traffic within an MCP architecture.

What API does Prototype use for server registration and lookup?

Prototype features a robust HTTP API built with FastAPI, providing clear endpoints for domain servers to register/unregister themselves and for clients to perform efficient service lookups.

Prototype

Name: Prototype
Author: nafshar2026

0•

Provides a centralized catalog server to track domain-specific Model-Controller-Provider servers and efficiently route incoming traffic.

This repository offers a foundational Model-Controller-Provider (MCP) architecture, centered around a catalog server designed to register and manage multiple domain-specific MCP servers. It features an in-memory registry for available services, allowing clients to perform lookups and traffic to be routed appropriately to various domain implementations. The architecture supports basic HTTP APIs for server registration and client lookups, laying the groundwork for scalable and highly available deployments on platforms like Azure Kubernetes Service with features such as persistent storage and auto-scaling.

主な機能

01Persistent Storage using SQLite database with automatic recovery

02High Availability with 3+ replicas and pod anti-affinity

03HTTP API with FastAPI endpoints for register/lookup/unregister

04Scalable via HPA configured for CPU/memory-based scaling

05Kubernetes Ready with liveness/readiness probes and resource limits

060 GitHub stars

ユースケース

01Building scalable and resilient microservice architectures on Kubernetes

02Developing a base architecture for integrating various backend systems (e.g., Salesforce)

03Centralized management and routing for multiple domain-specific services