Nouva MCP Server
Centralized repository for modular, portable skills and memory, enabling AI agents and IDEs to access personalized tools and memory via stdio or SSE transport.
README
Nouva MCP Server šš±
Nouva MCP (Model Context Protocol) Server is a centralized repository for modular, portable, and detachable Personalized Skills and Memory. It is written in Python (FastMCP) and runs on Gading's agent-host. You can run it locally or in a containerized environment.
The server supports dual transport:
- Stdio Transport: Used natively by OpenClaw on the local machine.
- SSE (Server-Sent Events) Transport: Runs an HTTP server on port
8000to be accessed by external clients like Cursor, Windsurf, or Hermes.
Architecture Overview
[AI Agent / IDE Client]
(OpenClaw, Cursor, Zed, Claude Code)
ā
ā¼ (via stdio / SSE)
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā Nouva MCP Server ā
ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā
ā ā Skills Engine ā ā (dynamic loader under src/skills/)
ā ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā ā
ā ā ā Memory Engine ā ā ā (pgvector recall + SQL analytics)
ā ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā ā
ā ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā ā
ā ā ā Persona Engine ā ā ā (startup persona bootstrap from markdown folders)
ā ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā ā
ā ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā ā
ā ā ā MCP Management ā ā ā (scaffolding & creating new skills)
ā ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā ā
ā ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā ā
ā ā ā Other Skills ā ā ā (custom tools, morning-report, etc.)
ā ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā ā
ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
Skill migration rules (portable by design)
- Python-based: tools should be implemented as native Python inside this repository.
- Self-contained: avoid wrappers that call scripts outside the repo.
- Secrets: keep secrets out of git and out of the repo by default. Prefer environment variables or host-mounted secret files.
Directory Structure
nouva-mcp-server/
āāā src/
ā āāā main.py # Entrypoint & Dynamic Skill Loader
ā āāā skills/ # Modular skill directories (native Python)
ā ā āāā memory_engine/
ā ā ā āāā README.md # Setup and operational notes for memory_engine
ā ā ā āāā SKILL.md # Agent routing guidance for memory tools
ā ā ā āāā memory_config.example.json # Template config for memory variables
ā ā ā āāā scripts/
ā ā ā ā āāā auto_sync.py # Memory auto-sync cron script
ā ā ā ā āāā query_memory.py # Hybrid search query engine
ā ā ā ā āāā query_analytics.py # Deterministic structured analytics executor
ā ā ā ā āāā db/ # DB helpers and init scripts
ā ā ā ā ā āāā init_db.py
ā ā ā ā ā āāā db_helper.py
ā ā ā ā ā āāā analytics_repo.py
ā ā ā ā āāā sync/
ā ā ā ā āāā summary_sync.py
ā ā ā ā āāā analytics_sync.py
ā ā ā āāā tools/
ā ā ā āāā query_memory.py # Tool: query_memory
ā ā ā āāā query_analytics.py # Tool: structured analytics executor
ā ā ā āāā sync_memory.py # Tool: sync_memory
ā ā āāā persona_engine/
ā ā ā āāā README.md # Persona setup and startup prompt integration
ā ā ā āāā SKILL.md # Agent guidance for persona loading
ā ā ā āāā scripts/
ā ā ā ā āāā util/
ā ā ā ā āāā persona_loader.py # Persona validation and prompt assembly
ā ā ā āāā tools/
ā ā ā āāā list_personas.py # Tool: mcp_list_personas
ā ā ā āāā get_persona_prompt.py # Tool: mcp_get_persona_prompt
ā ā āāā mcp_management/
ā ā ā āāā SKILL.md # Scaffolding guidelines (Resource)
ā ā ā āāā tools/
ā ā ā āāā create_skill.py # Tool: mcp_create_skill
ā āāā utils/
āāā personas/ # Private persona folders + public example template
āāā requirements.txt # Python dependencies
āāā ROADMAP_PLAN.md # Long-term development plan
Deployment & Running Options
You can run Nouva MCP Server either natively using Python or containerized via Docker.
Option A: Native Setup (Python)
1. Prerequisites (System Dependencies)
Install minimal system dependencies required for python packages compilation (e.g. psycopg2 for PostgreSQL):
apt update && apt install -y git build-essential libpq-dev python3-dev
2. Installation
Clone the repository and install the dependencies:
git clone https://github.com/nouverse-tech/nouva-mcp-server.git
cd nouva-mcp-server
pip install -r requirements.txt --break-system-packages
3. Configure Memory
Copy the memory configuration file:
# Setup memory config (includes database credentials)
cp src/skills/memory_engine/memory_config.example.json src/skills/memory_engine/memory_config.json
# Edit src/skills/memory_engine/memory_config.json with your local details:
# - database.host/port/name/user/password (or database.url for full connection string)
# - embedding.url and embedding.model
# - llm.url and llm.model
# - memory_paths.active_memory_dir
4. Running the Server (Stdio Mode)
python3 src/main.py --transport stdio
To enable one persona automatically for every new chat session:
python3 src/main.py --transport stdio --default-persona=nouva-example
If --default-persona is omitted, persona mode remains off and no startup persona prompt is injected by default.
Option B: Docker Setup
We provide a lightweight setup to build and run the MCP server in a Docker container.
1. Build the Docker Image
docker build -t nouverse/nouva-mcp-server:latest .
2. Run with Docker Compose (Production/Standard)
Ensure you have mapped your config files inside docker-compose.yml:
docker compose up -d
3. Run with Docker Compose for Development (Development Setup)
We provide a development configuration that spins up both the PostgreSQL (with pgvector extension) database and the MCP Server inside a single docker network.
-
Copy the configuration file:
cp src/skills/memory_engine/memory_config.example.json src/skills/memory_engine/memory_config.json(Note: The default credentials in
memory_config.example.jsonare pre-configured to match the local PostgreSQL container indocker-compose.dev.yml) -
Run the development docker compose:
docker compose -f docker-compose.dev.yml up -d -
Initialize the development database: Run the initialization script inside the container (or locally if you have python dependencies installed):
docker exec -it nouva-mcp-server-dev python3 src/skills/memory_engine/scripts/db/init_db.py
Client Integration
1. OpenClaw (Local Stdio Transport)
Add the following configuration to your OpenClaw MCP config (path depends on your installation):
{
"mcpServers": {
"nouva-mcp": {
"command": "python3",
"args": [
"/absolute/path/to/nouva-mcp-server/src/main.py",
"--transport",
"stdio"
]
}
}
}
2. Cursor
Cursor reads MCP server configs from:
- Project-scoped:
.cursor/mcp.json - User-scoped:
~/.cursor/mcp.json
Option A ā Connect via SSE (recommended if the server runs separately, e.g. Docker):
- Start the server in SSE mode on the host:
python3 src/main.py --transport sse --port 8000
- Add this to
.cursor/mcp.json:
{
"mcpServers": {
"nouva-mcp": {
"url": "http://<host>:8000/sse"
}
}
}
Option B ā Run via stdio (Cursor spawns the process locally):
{
"mcpServers": {
"nouva-mcp": {
"command": "python3",
"args": [
"/absolute/path/to/nouva-mcp-server/src/main.py",
"--transport",
"stdio"
]
}
}
}
Cursor MCP docs: https://cursor.com/docs/mcp
3. Zed
Zed stores MCP server configs in its settings file under context_servers. You can add this via UI ("Add Context Server") or edit settings manually.
Manual configuration example (~/.config/zed/settings.json), using stdio:
{
"context_servers": {
"nouva-mcp": {
"command": "python3",
"args": [
"/absolute/path/to/nouva-mcp-server/src/main.py",
"--transport",
"stdio"
],
"env": {}
}
}
}
Zed MCP docs: https://zed.dev/docs/ai/mcp.html
4. Other clients (Windsurf, Hermes, etc.)
Start the server in SSE mode:
python3 src/main.py --transport sse --port 8000
Then connect using:
- URL:
http://<host>:8000/sse - Transport: SSE
Do you need additional editor guidelines?
Connecting to the MCP server is enough for tool discovery. For best results, add a short routing rule in your agent instructions:
- Use
mcp_query_analyticsfor aggregation/time-series questions, but call it with structured arguments only after the agent parses the user's natural-language request. The analytics contract supports date lists, top values, weekday distributions, distinct-date counts, counts by period, grouped top values, and average importance. - Use
mcp_query_memoryfor detailed recall and context. - Use
mcp_get_persona_promptonly at new-session bootstrap time when a persona is explicitly selected or a default persona is configured.
Memory Engine Integration
For detailed setup instructions regarding the 2-lane memory architecture, pgvector recall, SQL analytics, embedding settings, database initialization, and memory sync operations, please refer to the Memory Engine README.
Persona Engine Integration
For startup persona packs, markdown folder structure, required files (IDENTITY.md, SOUL.md, USER.md), fail-fast validation, and --default-persona setup, please refer to the Persona Engine README.
Visual Graph with Obsidian
Since all daily logs and summaries are stored in a clean Markdown format (YYYY-MM-DD.md and _summaries/YYYY-MM-DD.summary.md), you can easily open the active/archived memory directories in Obsidian to explore your memories visually as an interconnected knowledge graph.

Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.