JSON Schema Validator MCP Server

# JSON Schema MCP Server Environment Configuration # Copy this file to .env and configure your settings # PostgreSQL Database Configuration # The server will fall back to local files if database is not available POSTGRES_HOST=localhost POSTGRES_PORT=5432 POSTGRES_DATABASE=jsonschema_mcp POSTGRES_USER=your_username POSTGRES_PASSWORD=your_password # Database Schema Management # WARNING: Only use POSTGRES_AUTO_RESET=true in development - it DELETES ALL DATA! POSTGRES_AUTO_CREATE_SCHEMA=true # Automatically create required tables POSTGRES_AUTO_RESET=false # WARNING: Drops and recreates all tables # Server Configuration # Uncomment and modify as needed # MCP_SERVER_PORT=stdio # MCP uses stdio by default # SSE_SERVER_HOST=0.0.0.0 # SSE server host # SSE_SERVER_PORT=8000 # SSE server port # Logging Configuration # LOG_LEVEL=INFO # DEBUG, INFO, WARNING, ERROR # LOG_FILE=logs/mcp_server.log # Log file path # Security Settings # MAX_SCHEMA_SIZE=1048576 # Maximum schema size in bytes (1MB) # MAX_JSON_SIZE=10485760 # Maximum JSON data size in bytes (10MB) # REQUEST_TIMEOUT=30 # HTTP request timeout in seconds # Development Settings # ENABLE_DEBUG=false # Enable debug mode # CORS_ALLOW_ORIGINS=* # CORS allowed origins for SSE server # PRETTY_PRINT_JSON=true # Pretty print JSON responses # Data Storage Settings # SCHEMAS_DIR=.schemas # Local schema storage directory # DATA_DIR=.data # Local data storage directory # CACHE_SIZE=1000 # Number of schemas to cache in memory # Example usage: # 1. Copy this file: cp .env.example .env # 2. Edit .env with your actual values # 3. Restart the server to apply changes # Notes: # - Database connection is optional - server works with files only # - All paths are relative to the project root # - Boolean values: true/false (lowercase) # - Uncomment lines by removing the # at the beginning