DawnMCP
Official# DawnMCP — Privacy-Conscious Repository Intelligence for AI Coding Assistants
[](https://nitrostack.ai)
[](https://nitrostack.ai)
[](https://dawnmcp-6a6d98d3-dawn-of-ai-srmist.app.nitrocloud.ai)
DawnMCP is a deployed MCP (Model Context Protocol) server that gives AI coding assistants — Claude, Cursor, and any MCP-compatible client — deep, grounded understanding of a codebase. Model inference runs through a local, open-source stack (Ollama), so code isn't sent to third-party cloud AI APIs, even though the server itself is hosted and shareable via a live endpoint.
**Built by Team Dawn of AI, SRMIST — Runner-Up, Agentic AI Hackathon 2026** (₹10L prize pool, organized by SRM School of Computing, Dept. of Computing Technologies, and NitroStack).
---
## Overview
**What it does:** DawnMCP indexes a repository and answers natural-language questions with grounded, file-and-line-cited responses — not guesses. It maintains persistent semantic memory across sessions, so project context isn't lost between conversations, and its agents can plan tasks, review code, and help debug by reasoning over the actual indexed codebase.
**Who it's for:** Teams and researchers working with proprietary or unpublished code — students on unpublished research, companies with sensitive IP, or anyone who wants AI coding assistance without routing their code through a third-party cloud LLM.
**What makes it work:**
- Model inference runs through a local Ollama instance (`qwen2.5-coder` for reasoning, `nomic-embed-text` for embeddings), with ChromaDB for vector storage — no code sent to external AI APIs for inference
- Built on the open MCP standard, not a closed plugin system — works with any MCP-compatible client
- Deployed on NitroCloud for a shareable, always-on endpoint
---
## Live Demo
🚀 **MCP endpoint:** https://dawnmcp-6a6d98d3-dawn-of-ai-srmist.app.nitrocloud.ai
Point any MCP-compatible client at this endpoint to try it directly — no local setup required.
```json
{
"mcpServers": {
"dawnmcp": {
"url": "https://dawnmcp-6a6d98d3-dawn-of-ai-srmist.app.nitrocloud.ai"
}
}
}
```
---
## Running It Yourself
### Prerequisites
- Node.js 18+
- An MCP-compatible client (Claude Desktop, Cursor, etc.)
### Setup
```bash
git clone https://github.com/dawnmcp/DawnMCP-1.git
cd DawnMCP-1
npm install
cp .env.example .env
npm run start
```
---
## Features
- 🔌 **MCP-native** — works with any MCP-compatible client
- 🛠️ **Tools, resources & prompts** — exposes structured capabilities to AI agents
- 🧠 **Persistent memory** — retains project context across sessions instead of starting fresh each time
- 🔐 **Secure by design** — secrets stay in environment variables, never in code
- ⚡ **Deployed on Nitrostack/NitroCloud** — reliable, hosted, and instantly shareable
---
## Tech Stack
MCP (Model Context Protocol) · Ollama (`qwen2.5-coder`, `nomic-embed-text`) · ChromaDB · TypeScript · NitroStack · NitroCloud
---
## Team
Built by **Dawn of AI**, SRM Institute of Science and Technology, KTR — during the Agentic AI Hackathon 2026.
---
## License
MIT © 2026
TDQS
Scored across 23 tools
Most tools have clearly distinct purposes, but there are close overlaps among repo_explain_architecture, repo_explain_project, and repo_summarize_repository, as well as between repo_analyze_repository and repo_scan_files. Descriptions help, but an agent could confuse these similar-sounding tools.
Names follow a consistent category_verb_noun pattern with underscores (e.g., documents_add_document, memory_search_memory, repo_index_repository). Minor deviations exist in plural/singular forms (search_documents vs add_document) and semantically similar verbs like 'explain' versus 'summarize', but overall the pattern is predictable.
At 23 tools, the set is on the heavier side. The four domains each justify their existence, but the repo category has 11 tools, with several overlapping analysis/explanation options that could be consolidated. Still, it's within a workable range.
Documents and memory have near-complete CRUD coverage (missing document update), and repo tools cover scanning, indexing, analysis, and querying. Agent tools provide plan/execute/review/debug lifecycle. Minor gaps like no repository unindex or knowledge graph deletion, but core workflows are well covered.