Back to Home
lanonasis icon

onasis-mcp-server

by lanonasis

Overview

Provides a unified API gateway and Model Context Protocol (MCP) server for enterprise memory management (Memory as a Service - MaaS), AI agent integration, and secure API key management, with real-time updates and workflow orchestration capabilities.

Installation

Run Command
node dist/unified-mcp-server.js

Environment Variables

  • SUPABASE_URL
  • SUPABASE_KEY
  • SUPABASE_SERVICE_KEY
  • JWT_SECRET
  • API_KEY_ENCRYPTION_KEY
  • OPENAI_API_KEY
  • REDIS_URL
  • OAUTH_CLIENT_SECRET
  • EMERGENCY_BOOTSTRAP_TOKEN
  • ONASIS_CORE_URL
  • LANONASIS_MAAS_URL
  • NODE_ENV
  • PORT
  • HOST

Security Notes

The server has critical security vulnerabilities. The '2025-08-23-PROGRESS-UPDATE.md' explicitly flags 'Authentication & Authorization Issues ⚠️' noting 'Current MCP implementation bypasses Core authentication entirely' and 'MCP calls database directly without proper JWT validation'. The `src/netlify/mcp.js` Netlify function hardcodes `organizationId: 'ADMIN_ORG'` and `userId: null`, allowing unauthenticated creation of memories and API keys. The `src/middleware/_middleware.js` includes a 'WARNING: Placeholder implementation - DO NOT DEPLOY TO PRODUCTION' for JWT validation. The `src/routes/emergency-admin.ts` creates an admin API key without login and warns to 'Remove this file after initial setup!'. Weak default `JWT_SECRET` and `EMERGENCY_BOOTSTRAP_TOKEN` values are present. The `EncryptionUtils` uses a hardcoded 'salt' which is a security anti-pattern. While `src/middleware/auth-aligned.ts` attempts to fix some authentication issues, the overall system, especially in its Netlify function deployments, is highly insecure and not safe for production as-is.

Similar Servers

Stats

Interest Score0
Security Score2
Cost ClassHigh
Avg Tokens1000
Stars0
Forks0
Last Update2026-01-02

Tags

API GatewayAI AgentsMemory ManagementModel Context ProtocolServer-Sent EventsWebSocketEnterpriseSupabaseOpenAIWorkflow OrchestrationCLI Integration