Tea Rags MCP
Enriches code chunks with authorship, timestamps, churn metrics, and task IDs extracted from commit history and git blame data.
Supports extracting GitHub task IDs from commit messages to provide context and linking between code and project issues.
Enables extraction of JIRA task IDs from commit messages to associate indexed code chunks with specific project tickets.
Integrates with Ollama for local, privacy-first embedding generation and semantic codebase search.
Supports OpenAI embedding models for semantic vectorization and high-performance code search.
Provides specialized Ruby AST-aware chunking to improve the accuracy and relevance of semantic search in Ruby codebases.
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., "@Tea Rags MCPsearch for where user authentication 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.
Your coding agent copies the first code it finds β not the right one.
TeaRAGs is an MCP server for code search that enriches every retrieved chunk with git history: authorship, churn, bug-fix rate, ownership. Your agent stops learning from hotspots and starts learning from stable, owned, battle-tested code.
π Full documentation Β· π 15-minute quickstart Β· π§ Core concepts
The Problem
1. Understanding a monorepo is expensive β for humans AND agents
Every new developer pays in hours. Every fresh agent session pays in tokens. Naming conventions, domain logic, local idioms β all of it has to be rebuilt from scratch, every time.
2. Bad code hygiene is a tax on your agent
Confusing names mean the agent reads more files. More files mean more tokens, slower responses, and a higher chance of picking the wrong example. Your codebase's technical debt is now your AI bill.
3. Agents can't tell stable code from a hotspot
Standard code search ranks by embedding similarity alone. It doesn't know which function gets bug-fixed every sprint, which module hasn't been touched in two years, or whose name is on the commits. So the agent copies whatever looks similar β including the broken examples.
The Solution
TeaRAGs gives your agent two things it can't get from vanilla code search.
1. Every chunk carries its own history
Retrieved code comes with signals about who wrote it, how stable it is, how often it gets bug-fixed, and how impactful a change would be. Semantic similarity stops being the whole answer β it becomes the floor.
2. Pre-built skills, not just raw tools
TeaRAGs ships agent skills β ready-made playbooks that tell your agent when and how to use the signals. No prompt engineering required:
exploreβ orient in an unfamiliar codebasedata-driven-generationβ write code backed by stable, owned templatesrisk-assessmentβ know what you'd break before you break itrefactoring-scanΒ·bug-huntΒ·pattern-searchβ and more
Install the plugin, your agent learns the workflow. See all skills β
Bonus: dinopowers β a companion plugin with 10 wrappers over
superpowers:* skills (Jesse Vincent's
skills library for Claude Code) that inject tea-rags signals into brainstorming,
planning, debugging, TDD, review, and completion flows. Mean eval delta +71pp
across 136 cases.
Learn more β
Use Cases
π‘οΈ Safe code generation
Your agent writes new code backed by stable, canonical templates β modules
with a low bug-fix rate, long stability, and a clear owner. No more copying from
last sprint's hotspot. Skill: data-driven-generation Β·
Why stable code is safer β
π§ Refactoring planning & problem-pattern discovery
Find the 5% of code responsible for 80% of incidents. High churn + high
bug-fix rate + concentrated ownership = your next production issue β and your
next refactoring candidate. Skills: refactoring-scan, bug-hunt
π― Risk assessment before changes
Before modifying a function, the agent checks who depends on it, how often it
breaks, and what its ticket history says. Know the blast radius before you
blast. Skill: risk-assessment Β·
Coupling & blast radius theory β
πΊοΈ Learning an unfamiliar codebase
Ask questions instead of reading directory trees. "How does auth work?"
returns the stable, canonical implementation with its history attached β not
a random similar-looking snippet. Skill: explore
How It Works
flowchart LR
User([π€ You])
subgraph mcp["TeaRAGs MCP Server"]
Agent[π€ Agent<br/>runs skills]
TeaRAGs[π΅ TeaRAGs<br/>search Β· enrich Β· rerank]
Agent <--> TeaRAGs
end
Qdrant[(ποΈ Qdrant<br/>vector DB)]
Embeddings[β¨ Embeddings<br/>Ollama/OpenAI]
Codebase[π Your Codebase<br/>+ Git History]
User <--> Agent
TeaRAGs <--> Qdrant
TeaRAGs <--> Embeddings
TeaRAGs <--> CodebaseYou talk to your agent. The agent runs a TeaRAGs skill. TeaRAGs searches your code, enriches each result with git history, and ranks by what the skill needs β stability, ownership, risk, or pure relevance.
What You Get
𧬠Trajectory-aware retrieval β the only open-source code RAG that scores results by git history, not just embedding similarity
π Ships with agent skills β 6 ready-made playbooks for exploration, generation, risk assessment, and index management (plus 2 internal strategies)
π Local-first, privacy-first β works fully offline with Ollama; your code never leaves your machine (cloud providers optional)
π Built for monorepos β AST-aware chunking across 10+ languages, incremental reindexing, parallel pipelines, millions of LOC tested
Who It's For
Developers in large monorepos β where "find similar code" returns a dozen near-duplicates and you need the canonical one
Solo devs doing agentic development β agent-driven workflows produce bursts of micro-commits that wreck churn metrics. TeaRAGs ships a GIT SESSIONS mode (
TRAJECTORY_GIT_SQUASH_AWARE_SESSIONS=true) that groups commits by(author, time gap)so a 20-commit refactor session counts as one. Churn, bug-fix rate, and ownership stay meaningful even with a single human + an agent as the only contributors.Tech leads worried about AI code quality β who want their team's agents to learn from stable modules, not from last sprint's hotspot
Privacy-sensitive teams β finance, healthcare, defense, or anyone who can't send source code to a cloud API
Not for: repos without git history (no signal to enrich) or teams that only need autocomplete (use Copilot).
π Quick Start
Inside Claude Code, install the TeaRAGs plugins and run the setup wizard:
/plugin marketplace add artk0de/TeaRAGs-MCP
/plugin install tea-rags-setup@tea-rags
/tea-rags-setup:installThen install the skills plugin (Claude-only, final step):
/plugin install tea-rags@tea-ragsOptionally install dinopowers for wrappers over superpowers:* skills:
/plugin install dinopowers@tea-ragsIndex your codebase:
/tea-rags:indexAsk your agent anything: "How does auth work in this project?", "Find stable examples of retry logic", "What should I know before touching the payment module?".
For other MCP clients, CI, or air-gapped setups, see the
manual install
(Node + npm install -g tea-rags + Ollama/ONNX/OpenAI/Cohere/Voyage).
π Documentation
I want to⦠| Start here |
Get it running | Quickstart (15 min) β install, index, first query |
Understand the concept | Core Concepts β vectorization, trajectory enrichment, reranking |
See what my agent can do | Skills β 6 ready-made agent playbooks for exploration, generation, risk |
Look under the hood | Architecture β pipelines, data model, reranker internals |
Learn the theory | Knowledge Base β RAG, code search, software evolution |
π€ Contributing
See CONTRIBUTING.md for workflow and conventions.
π Acknowledgments
Built on a fork of mhalder/qdrant-mcp-server β clean architecture, solid tests, open-source spirit. And its ancestor qdrant/mcp-server-qdrant. Code vectorization inspired by claude-context (Zilliz).
Feel free to fork this fork. It's forks all the way down. π’
βοΈ License
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.
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/artk0de/TeaRAGs-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server