1. Conduid
  2. Data
  3. Summerrs Admin
MCP server · Data

Summerrs Admin

Full-stack admin system in Rust featuring JWT/RBAC auth, database sharding, multi-tenancy, AI gateway, MCP server and Socket.IO.

Unclaimed data
34Low

Scored 5 months ago · breakdown

About Summerrs Admin

Summerrs Admin is an MCP server in the Data category: full-stack admin system in Rust featuring JWT/RBAC auth, database sharding, multi-tenancy, AI gateway, MCP server and Socket.IO.

Install

From source
git clone https://github.com/ouywm/summerrs-admin

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Summerrs Admin

Powered by Claude · Grounded in docs

I know everything about Summerrs Admin. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

Summerrs Admin

中文 | English

Full-stack Rust admin system · LLM relay gateway, database sharding, multi-tenant isolation, MCP service, declarative macros — all in one binary

License Rust Edition GitHub stars zread

Core Capabilities · Architecture · Project Structure


What It Is

summerrs-admin is a production-grade admin system written entirely in Rust, built on top of the Summer framework (a Spring-style application skeleton for Rust). It bundles capabilities that usually require a whole backend team to assemble — authentication, multi-tenancy, AI gateway, real-time messaging, object storage, declarative auditing — into a single binary via a plugin composition model. Use what you need, ignore what you don't.

It is not a demo, nor a showcase of any single component — it is a complete, self-contained, deployable backend foundation.


How It Differs From Similar Projects

The market generally splits into CRUD scaffolds, AI gateways, and sharding middleware. Few projects combine them. summerrs-admin puts four things in one place:

Capability Typical This Project
LLM Relay Gateway A separate project (new-api, one-api, AxonHub) Embedded as the summer-ai crate, sharing auth / billing / audit with the admin
Database Sharding Bolted on via ShardingSphere / Vitess summer-sharding rewrites SQL transparently — no business code changes
MCP Service A standalone MCP server process summer-mcp introspects business schema directly; AI assistants generate CRUD
Declarative Audit & Rate Limiting Middleware + handwritten code #[login] #[has_perm] #[rate_limit] — single-line attributes

Not every project needs all of this. But once you need any two of them, putting them in the same process saves an entire layer of ops.


Architecture

The system is built around plugin composition. crates/app/src/main.rs is the assembly point — 17 plugins fed into App::new() in order:

                    HTTP 8080
                       │
                       ▼
        ┌──────────────────────────────────┐
        │  Tower middleware (CORS /        │
        │  compression / panic guard /     │
        │  client IP extraction)           │
        └──────────────┬───────────────────┘
                       │
        ┌──────────────┼──────────────────┐
        ▼              ▼                  ▼
   /api/* (JWT)    /v1/*  (API key)   default
   summer-system  summer-ai-relay     handler
   summer-ai-admin (OpenAI/Claude/    auto-grouped
                   Gemini ingress)
                       │
                       ▼
        ┌──────────────────────────────────┐
        │  Declarative macro layer         │
        │  #[login] #[has_perm]            │
        │  #[has_role] #[rate_limit]       │
        │  #[operation_log]                │
        └──────────────┬───────────────────┘
                       │
                       ▼
        ┌──────────────────────────────────┐
        │  Sharding / SQL rewrite layer    │
        │  Tenant context / encrypt / mask │
        └──────┬─────────────┬─────────────┘
               ▼             ▼
          PostgreSQL 17    Redis 7
          (primary)        (sessions / cache / rate limit)
                                │
                                ▼
                    Socket.IO / background jobs / S3

Plugin roster (17): WebPlugin · SeaOrmPlugin · RedisPlugin · SummerShardingPlugin · SummerSqlRewritePlugin · JobPlugin · MailPlugin · SummerAuthPlugin · PermBitmapPlugin · SocketGatewayPlugin · Ip2RegionPlugin · S3Plugin · BackgroundTaskPlugin · LogBatchCollectorPlugin · McpPlugin · SummerAiRelayPlugin · SummerAiBillingPlugin


Core Capabilities

Authentication & Authorization

  • Multi-algorithm JWT — HS256 / RS256 / ES256 / EdDSA, key rotation supported
  • Bitmap RBAC — bit-wise permission checks, O(1)
  • Declarative macros — #[login] #[has_perm("user:create")] #[has_role("admin")] #[public]
  • Session governance — concurrent login limits, per-device caps, token refresh, force logout

Multi-Tenancy & Database

  • Four isolation tiers

    Mode Suited for Mechanism
    shared_row Most SaaS SQL rewrite injects tenant_id filter
    separate_table Mid isolation Physical sharding (user_001 / user_002)
    separate_schema Strong isolation PostgreSQL schema-level separation
    separate_database Full isolation Each tenant gets its own physical database
  • SQL rewrite engine — tenant context injected transparently, business code untouched

  • CDC pipeline — change data capture across tenants

  • Encryption / masking / audit — built into the sharding layer, applied before persistence

AI Gateway (summer-ai)

  • Three ingress protocols

    Protocol Path Compatibility
    OpenAI /v1/chat/completions /v1/responses /v1/models native
    Claude /v1/messages native
    Gemini /v1beta/models/{target} native
  • 40+ upstream providers — implemented as ZST (zero-sized type) adapters, zero runtime overhead

  • 6-dimension dynamic routing — protocol family / endpoint / credentials / model mapping / extra headers / routing strategy

  • Three-phase billing — Reserve → Settle → Refund, atomic

  • Automatic failover — retry across channels by priority on failure (streaming requests do not retry)

  • Hot-reload — config lives in the database, no restart needed

  • Full tracing — lifecycle logs including every retry attempt

MCP Server Integration

  • Schema discovery — AI assistants can introspect the database schema
  • Code generation — generate CRUD modules through dialogue
  • Menu / dictionary auto-deploy — prompt-driven persistence
  • Underlying — built on rmcp (the official Rust MCP SDK), supporting both stdio and streamable-http transports

Real-time & Background Processing

  • Socket.IO — bidirectional real-time, session state in Redis (horizontally scalable)
  • Background task queue — typed jobs, 4 workers by default, capacity 4096
  • Batch logging — operation logs flushed asynchronously, off the hot path
  • Cron jobs — driven by tokio-cron-scheduler

Storage & Utilities

  • S3-compatible storage — AWS S3 / MinIO / RustFS, multipart upload up to 5 GB
  • IP geolocation — IP2Region xdb embedded, login logs auto-attributed
  • i18n — compile-time, currently zh / en
  • Rate limiting — 5 algorithms: fixed window, sliding window, token bucket, leaky bucket, Lua script
  • OpenAPI docs — at /docs, with Swagger UI

Project Structure

summerrs-admin/
├── crates/
│   ├── app/                          # binary entry, assembles all plugins
│   ├── summer-admin-macros/          # declarative macros (#[login] / #[has_perm] etc.)
│   ├── summer-auth/                  # JWT auth + path policy
│   ├── summer-common/                # shared types & utilities
│   ├── summer-domain/                # domain models (entities / VOs)
│   ├── summer-ai/                    # AI gateway (relay + billing + admin)
│   │   ├── core/                     # protocol core
│   │   ├── model/                    # data models
│   │   ├── relay/                    # relay engine
│   │   ├── admin/                    # admin API
│   │   └── billing/                  # billing & settlement
│   ├── summer-sharding/              # sharding / multi-tenancy middleware
│   ├── summer-sql-rewrite/           # SQL rewrite engine
│   ├── summer-mcp/                   # MCP server
│   ├── summer-plugins/               # S3 / IP2Region / background jobs etc.
│   └── summer-system/                # system business (RBAC / users / menus / Socket.IO)
│       └── model/
├── config/                           # multi-env configs (dev / prod / test)
├── sql/                              # database source of truth
│   ├── sys/                          # system domain (users / menus / perms / logs)
│   ├── tenant/                       # tenant control plane
│   ├── biz/                          # B/C-side business
│   ├── ai/                           # AI gateway schema
│   └── migration/                    # one-shot migration scripts
├── doc/                              # deployment / migration / technical guides
├── docs/                             # research, surveys, reference materials
├── locales/                          # i18n resources
├── build-tools/                      # fmt / clippy / pre-commit scripts
├── docker-compose.yml                # one-shot stack: postgres + redis + rustfs + app
└── Dockerfile                        # multi-stage build

If this project helps you, a Star is appreciated.

Report an issue · Start a discussion

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Summerrs Admin

How do I install Summerrs Admin?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Summerrs Admin safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Summerrs Admin still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.