reaatech/mcp-catalog
These packages let you run an internal registry where MCP servers can register themselves, be discovered by capability, and have their health monitored automatically. You'd adopt them to solve the problem of finding and managing MCP servers across a team or organization without relying on a public directory or ad‑hoc documentation. The most distinctive thing is that the catalog itself is exposed as an MCP server, so any MCP client can query it using the same protocol the registered servers speak.
Packages
1 package
@reaatech/mcp-catalog-shared
Shared TypeScript type definitions and Zod validation schemas for MCP Catalog domain entities (`Server`, `Capability`, `Tool`, `Resource`, `User`, `ApiKey`, `AccessPolicy`, `HealthCheck`, `AuditLog`) and their create/update/search operations. This types-only module depends solely on `zod` and provides canonical interfaces and runtime validation schemas for type-safe consumption and production of MCP Catalog domain objects.
- status
- published
- published
- 22 days ago
Comments
Sign in with GitHub to comment and vote.
Loading comments…
