rag-legacy
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@rag-legacyshow me how token refresh is implemented"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
vite-mf-monorepo-rag
Local RAG system for semantic recall of the vite-mf-monorepo legacy codebase from Claude Code.
Goal
Allow Claude Code, when working in the Next.js project, to find legacy code and patterns by meaning — not by filename. Instead of searching by file name or regex, Claude Code calls recall("how was token refresh handled?") and gets back the most semantically relevant chunks from the legacy codebase.
Related MCP server: RAGex
How it works
1. INDEXING (one-time, then re-run when legacy changes)
pnpm index
→ walks vite-mf-monorepo (349 files)
→ chunks each file into overlapping segments
→ embeds each chunk via nomic-embed-text (Ollama, local)
→ stores chunks + embeddings in MongoDB Atlas (legacy_chunks)
2. RECALL (at query time, triggered by Claude Code)
Claude Code calls the recall() MCP tool with a natural language query
→ query is embedded via nomic-embed-text
→ vector search in MongoDB Atlas finds the top N most similar chunks
→ Claude Code receives file paths + content ranked by semantic similarityStack
Component | Choice |
Embeddings | nomic-embed-text via Ollama (local, 768 dimensions) |
Vector store | MongoDB Atlas M0 — |
Vector index | Atlas Vector Search — cosine similarity, filters on |
MCP server | Local stdio server exposing |
Language | TypeScript |
Prerequisites
Ollama
Ollama must be running locally — it handles all embedding generation.
Download and install from ollama.com
Pull the embedding model:
ollama pull nomic-embed-textVerify:
ollama listOllama must be running in the background before indexing or using recall.
Structure
src/
indexer/
index.ts # indexing pipeline entry point
walk.ts # recursive file walker with ignore rules
classify.ts # classifies files as app or package
chunk.ts # splits large files into overlapping chunks
retriever/
recall.ts # embeds query + runs Atlas vector search
mcp/
server.ts # stdio MCP server exposing recall() to Claude CodeIndexed projects
Legacy (
vite-mf-monorepo) — indexed in MongoDB AtlasNext (
nextjs-multizone-tmdb) — read live by Claude Code, not indexed
Indexing rules
Indexed: .ts, .tsx, .md — source files and config files
Ignored: node_modules, dist, __mf__temp, .netlify, scripts/, *.test.ts, *.spec.ts, *.d.ts, *.css, *.json, *.sh, .env*, vitest.config.ts, vitest.setup.ts
Setup
pnpm install
cp .env.example .env # fill in MONGODB_URI and LEGACY_PATHEnvironment variables
Variable | Description |
| MongoDB Atlas connection string |
| Absolute path to the |
MCP server setup (nextjs-multizone-tmdb)
The MCP server must be registered in the Next.js project so Claude Code can call recall().
Create .mcp.json at the root of nextjs-multizone-tmdb:
{
"mcpServers": {
"rag-legacy": {
"type": "stdio",
"command": "pnpm",
"args": ["--prefix", "/absolute/path/to/vite-mf-monorepo-rag", "run", "mcp"],
"env": {
"MONGODB_URI": "your_mongodb_uri",
"LEGACY_PATH": "/absolute/path/to/vite-mf-monorepo"
}
}
}
}Then in Claude Code, run /mcp and accept the server when prompted.
Scripts
pnpm index # run the full legacy indexing pipeline
pnpm mcp # start the MCP server (Claude Code does this automatically)
pnpm build # compile TypeScript
pnpm lint # ESLint
pnpm type-check # type check without compilationRe-indexing
Run pnpm index whenever the legacy codebase changes. The pipeline clears legacy_chunks and re-indexes everything from scratch.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides semantic code intelligence to help users search, navigate, and analyze entire codebases using plain English. It enables Claude to perform architectural overviews, bug detection, and refactor suggestions through local semantic search and keyword indexing.MIT
- FlicenseNot gradedqualityFmaintenanceGives Claude semantic search superpowers to find and reuse existing patterns in your codebase.16
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving Claude Code conversation history via hybrid semantic and keyword search, allowing the agent to access its own past interactions.4MIT
- AlicenseAqualityDmaintenanceEnables semantic search over codebases using natural language queries, returning relevant code snippets with source locations. Integrates with Claude Code for automatic codebase exploration.11MIT
Related MCP Connectors
Code intelligence for coding agents: semantic, AST, graph, and full-text search. 279+ languages.
Token-efficient search for coding agents over public and private documentation.
Connect your team's living knowledge base — docs, data, issues, CRM — to Claude and ChatGPT.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/fubaritico/vite-mf-monorepo-rag'
If you have feedback or need assistance with the MCP directory API, please join our Discord server