reaatech/multi-tenant-mcp
These packages let you run a single MCP server that serves multiple tenants, with each tenant getting its own rate limits, tool visibility, cost tracking, and isolated artifact storage. You'd adopt them to avoid standing up a separate MCP server per customer while still enforcing per-tenant boundaries on usage, access, and billing. The distinctive thing is that every concern—tenant resolution, rate limiting, visibility, cost accounting, artifact storage, config isolation, and observability—is a separate package you compose into a single middleware function that wraps any MCP server's request handlers.
Packages
9 packages
@reaatech/multi-tenant-mcp-artifact-store
- status
- published
- published
- 19 days ago
@reaatech/multi-tenant-mcp-config-isolation
- status
- published
- published
- 19 days ago
@reaatech/multi-tenant-mcp-cost-accounting
- status
- published
- published
- 19 days ago
@reaatech/multi-tenant-mcp-middleware
- status
- published
- published
- 19 days ago
@reaatech/multi-tenant-mcp-observability
- status
- published
- published
- 19 days ago
@reaatech/multi-tenant-mcp-rate-limiter
- status
- published
- published
- 19 days ago
@reaatech/multi-tenant-mcp-tenant-resolver
- status
- published
- published
- 19 days ago
@reaatech/multi-tenant-mcp-tool-visibility
- status
- published
- published
- 19 days ago
@reaatech/multi-tenant-mcp-types
- status
- published
- published
- 19 days ago
Comments
Sign in with GitHub to comment and vote.
