ContextBase (MCP Server)

What is ContextBase (MCP Server)?

ContextBase (MCP Server) is a Model Context Protocol server for AI agents, assistants, and applications. It stores, retrieves, and manages per-user context using a simple API, built with TypeScript, Fastify, Prisma ORM, PostgreSQL, and Redis.

How to use ContextBase (MCP Server)?

Install Node.js v14+, PostgreSQL, and Redis. Clone the repository, install dependencies, configure environment variables (DATABASE_URL, REDIS_HOST, REDIS_PORT, JWT_SECRET, PORT), run database migrations with npx prisma migrate dev, then start the server with npm start or docker-compose up. Use the provided REST API endpoints (e.g., POST /api/auth/register, POST /api/memory) to register users, login, and manage memory objects.

Key features of ContextBase (MCP Server)

• Secure user authentication using JWT and bcrypt
• API endpoints for storing and retrieving memory data
• Comprehensive logging of user actions
• PostgreSQL for persistent storage
• Redis for high-performance caching
• Modern tech stack: TypeScript, Fastify, Prisma ORM

Use cases of ContextBase (MCP Server)

• AI assistants maintaining per-user conversation history
• Applications storing user-specific context across sessions
• Managing and retrieving user memories via a RESTful API
• Auditing user actions with a built-in logging system

FAQ from ContextBase (MCP Server)

What runtime and dependencies are required?

Node.js v14 or higher, PostgreSQL, and Redis are required. Docker and Docker Compose can be used for containerized deployment.

How does authentication work?

The server uses JWT and bcrypt. Users can register via POST /api/auth/register and login via POST /api/auth/login to obtain a token.

What data can be stored and retrieved?

Memory objects can be created, read, updated, and deleted via REST endpoints (/api/memory). Logs of user actions are accessible at /api/logs.

Where is data persisted?

Per-user context is stored in PostgreSQL; Redis is used as a caching layer for performance.

What transport protocol does the server use?

The server exposes a REST API over HTTP, listening on a configurable port (default 3000). No WebSocket or other transports are mentioned.