Nouz
Give your agent semantic search and DAG-structured knowledge over an Obsidian vault while you build specs, docs, and long-running projects.
Overview
Nouz MCP is a MCP server for the Build phase that adds semantic search and DAG-organized Obsidian vault knowledge to your coding agent.
What is this MCP server?
- Semantic knowledge engine for Obsidian with auto-classification and DAG hierarchy
- PyPI nouz-mcp v2.3.0 with configurable modes: luca, prizma, sloi (default prizma)
- OBSIDIAN_ROOT vault path plus optional embeddings via OpenAI, GigaChat, or LM Studio
- EMBED_ENABLED toggle and EMBED_API_URL default http://127.0.0.1:1234/v1 for local stacks
- Turns a solo builder vault into MCP-queryable context instead of paste-heavy prompts
- Server version 2.3.0 on PyPI identifier nouz-mcp
- Three named server modes: luca, prizma, sloi
- Default embedding API URL http://127.0.0.1:1234/v1 in schema
What problem does it solve?
Solo builders store plans in Obsidian but their agent cannot reliably search, classify, or traverse linked notes without copying chunks into every chat.
Who is it for?
Indie builders with a mature Obsidian vault who use Claude Code or Cursor daily and want local or BYOK embeddings.
Skip if: Teams on Notion or Google Docs only, or beginners who do not want to manage OBSIDIAN_ROOT paths and embedding providers.
What do I get? / Deliverables
After configuring nouz-mcp, your agent queries a classified, embedding-aware view of your vault through standard MCP tools.
- MCP-accessible semantic queries over classified Obsidian notes
- Configurable Nouz server (modes luca / prizma / sloi)
- Reduced copy-paste context loading during agent-driven builds
Recommended MCP Servers
Journey fit
Obsidian-backed agent memory is canonically Build agent-tooling, but the same vault supports Idea notes, Ship runbooks, and Operate incident logs. Agent-tooling subphase reflects MCP tools that extend what Claude Code and Cursor can retrieve from your personal knowledge base.
How it compares
Obsidian-centric semantic RAG MCP, not a generic filesystem listing tool or a single static SKILL.md playbook.
Common Questions / FAQ
Who is Nouz MCP for?
Solo builders and power users who organize product knowledge in Obsidian and want semantic MCP access from their AI coding agent.
When should I use Nouz MCP?
Use it during Build and across the journey whenever agent tasks need grounded retrieval from your vault—specs, research, launch copy, or ops notes.
How do I add Nouz MCP to my agent?
Install PyPI nouz-mcp, set OBSIDIAN_ROOT and MODE, configure EMBED_* variables if embeddings are on, then register the stdio server in your MCP client.