Architecture Overview
This section provides detailed technical documentation of Seed's internal architecture.
System Design
Seed is built as an Express-based HTTP server with middleware-driven authentication and MCP protocol implementation.
Core Components
- Authentication Middleware - JWT validation on all requests except public paths
- JWKS Service - JSON Web Key Set management with caching
- OAuth Proxy - OAuth 2.1 implementation with PKCE support
- MCP Server - Model Context Protocol implementation using @modelcontextprotocol/sdk
- Client Store - Redis-backed storage for registered clients
- Session Management - UUID-based session tracking
Technology Stack
| Component | Technology | Purpose |
|---|---|---|
| Runtime | Node.js 24+ | JavaScript runtime |
| Language | TypeScript | Type safety and developer experience |
| Framework | Express 5.x | HTTP server |
| MCP SDK | @modelcontextprotocol/sdk | MCP protocol implementation |
| JWT | jose | JWT validation and JWKS handling |
| Storage | ioredis | Redis client for sessions and DCR |
| Testing | Vitest | Unit and integration testing |
Project Structure
src/
├── config/ # Configuration management
├── middleware/ # Express middleware (auth)
├── mcp/ # MCP server and tools
├── routes/ # HTTP route handlers
├── services/ # Business logic (JWKS, Redis, etc.)
└── types/ # TypeScript type definitionsExplore Further
- Authentication Flow - How JWT validation works
- OAuth 2.1 Implementation - Authorization code flow with PKCE
- MCP Server Design - Tool registration and session management
- Session Management - Session lifecycle and storage
- Configuration System - Environment-based configuration