Glanser Guidelines MCP Server
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., "@Glanser Guidelines MCP Serversearch for error handling best practices in our guidelines"
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.
Glanser Guidelines MCP Server
Semantic search over the team's coding guidelines corpus. Powered by FastMCP + ChromaDB + sentence-transformers (all-MiniLM-L6-v2). 100% free — no API keys, no external services, runs fully offline after setup.
Folder Structure
mcp-server/
├── server.py ← MCP server (run this on the host)
├── ingest.py ← One-time ingestion script
├── requirements.txt ← Python dependencies
├── documents/ ← Drop your .md guideline files here
│ └── CODING_GUIDELINES.md
└── chroma_db/ ← Created automatically by ingest.py (do not edit)Setup (run once on the host machine)
1. Install dependencies
pip install -r requirements.txt
sentence-transformerswill download theall-MiniLM-L6-v2model (~80 MB) on first run and cache it. Subsequent runs are fully offline.
2. Add your documents
Copy markdown files into the documents/ folder:
cp /path/to/CODING_GUIDELINES.md documents/3. Ingest (embed once, saved to disk)
python ingest.pyThis reads every .md file in documents/, embeds each section, and
persists the vectors to chroma_db/. You only re-run this when adding
a new document.
Useful flags:
python ingest.py --file documents/NEW_DOC.md # add a single new doc
python ingest.py --reset # wipe and re-ingest everything
python ingest.py --list # see what is currently indexed4. Start the server
python server.pyServer starts on http://0.0.0.0:8000.
Hosting (team access)
Deploy to Railway or Render (both have free tiers):
Push this
mcp-server/folder to a git repoCreate a new service pointing to that repo
Set start command:
python server.pyMount a persistent volume at
/app/chroma_db(so embeddings survive deploys)Run
python ingest.pyonce via the host console after deploy
Railway/Render automatically provision an HTTPS URL like:
https://glanser-guidelines-mcp.railway.app
Team .mcp.json entry
Each team member adds this to their .mcp.json:
{
"mcpServers": {
"coding-guidelines": {
"type": "http",
"url": "https://your-hosted-domain.com/mcp"
}
}
}Available Tools
Tool | What it does |
| Semantic search across all docs — use this first |
| Fetch full content of a specific section |
| Browse all section titles across the corpus |
| Filter rules by |
| See all indexed documents and their section counts |
Adding a New Document
# 1. Copy the new doc
cp NEW_GUIDELINES.md documents/
# 2. Ingest only the new file (does not re-embed existing docs)
python ingest.py --file documents/NEW_GUIDELINES.md
# 3. No server restart needed — ChromaDB is queried liveLocal dev / testing (without hosting)
{
"mcpServers": {
"coding-guidelines": {
"type": "http",
"url": "http://localhost:8000/mcp"
}
}
}This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
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/Vbridge7/MCP-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server