CodeContext
Enables AI coding assistants to automatically detect and inject team-specific codebase patterns (e.g., error handling, imports, naming conventions) via the Model Context Protocol, ensuring suggestions follow project conventions.
README
<div align="center">
π§ CodeContext
AI Coding Context Layer β Make AI assistants understand your team's codebase patterns
Features β’ Quick Start β’ Architecture β’ API Reference β’ Contributing
</div>
π― The Problem
AI coding assistants like Cursor and Copilot are powerful, but they don't understand your team's unique patterns:
- Your error handling conventions
- Your import style preferences
- Your validation approach
- Your authentication patterns
Every suggestion requires mental translation to match your codebase.
β¨ The Solution
CodeContext automatically detects your codebase patterns and injects them as context into AI assistants via the Model Context Protocol (MCP). Now every AI suggestion follows your team's conventions out of the box.
π Features
8 Pattern Types Detected
| Category | Pattern Types | Detection Method |
|---|---|---|
| Code Style | Error Handling, Imports, Naming, Structure | Rules-based (instant) |
| Frameworks | API Format, Validation, Database, Auth | Hybrid (rules + LLM fallback) |
Key Capabilities
- π AST-Powered Analysis β Deep code parsing with Babel for accurate pattern detection
- π€ Hybrid Detection β Rules-based first, LLM (Groq) fallback for complex patterns
- β‘ Real-time Indexing β Background processing with Redis queue
- π MCP Protocol β Native integration with Cursor, Copilot, and more
- π GitHub OAuth β Seamless onboarding and repository access
- π Dashboard β View detected patterns, confidence scores, and usage analytics
ποΈ Architecture
flowchart TB
subgraph Input["π₯ Input"]
GH[GitHub Repository]
end
subgraph Core["π§ CodeContext Engine"]
IDX[Indexing Queue<br/>Redis/Upstash]
AST[AST Parser<br/>Babel]
DET[Pattern Detectors<br/>8 Types]
LLM[LLM Fallback<br/>Groq]
CTX[Context Generator]
end
subgraph Storage["πΎ Storage"]
DB[(PostgreSQL<br/>Supabase)]
end
subgraph Output["π€ Output"]
MCP[MCP Server]
DASH[Dashboard]
end
subgraph Clients["π€ AI Clients"]
CUR[Cursor]
COP[Copilot]
OTHER[Other MCP Clients]
end
GH --> IDX
IDX --> AST
AST --> DET
DET --> LLM
DET --> DB
LLM --> DB
DB --> CTX
CTX --> MCP
DB --> DASH
MCP --> CUR
MCP --> COP
MCP --> OTHER
π¦ Tech Stack
| Layer | Technology |
|---|---|
| Frontend | Next.js 14 (App Router), TypeScript, Tailwind CSS |
| Backend | Next.js API Routes, NextAuth.js |
| Database | PostgreSQL (Supabase) |
| Queue | Redis (Upstash) |
| AST Parsing | @babel/parser, @babel/traverse |
| LLM | Groq (llama-3.3-70b-versatile) |
| MCP | @modelcontextprotocol/sdk |
π Quick Start
Prerequisites
- Node.js 18+
- PostgreSQL database (we recommend Supabase)
- Redis instance (we recommend Upstash)
- GitHub OAuth App
- Groq API key (free tier: 14,400 req/day)
1. Clone & Install
git clone https://github.com/bhasinagam/ContextBridge.git
cd ContextBridge
npm install
2. Configure Environment
cp .env.example .env.local
Edit .env.local with your credentials:
| Variable | Description | Where to Get |
|---|---|---|
DATABASE_URL |
PostgreSQL connection string | Supabase β Settings β Database |
UPSTASH_REDIS_REST_URL |
Redis REST URL | Upstash β Redis β REST API |
UPSTASH_REDIS_REST_TOKEN |
Redis REST token | Same as above |
NEXTAUTH_SECRET |
Random 32-byte secret | Run: openssl rand -base64 32 |
GITHUB_CLIENT_ID |
OAuth App client ID | GitHub β OAuth Apps |
GITHUB_CLIENT_SECRET |
OAuth App secret | Same as above |
GROQ_API_KEY |
Groq API key | Groq Console |
3. Set Up Database
Run the schema in your Supabase SQL editor:
-- Contents of src/lib/db/schema.sql
Or use the Supabase dashboard to import src/lib/db/schema.sql.
4. Run Development Server
npm run dev
Open http://localhost:3000 to access the dashboard.
π MCP Integration
Using with Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"codecontext": {
"url": "http://localhost:3000/api/mcp/context",
"headers": {
"X-API-Key": "your-api-key"
},
"defaultParams": {
"repo_id": "your-repo-id"
}
}
}
}
API Usage
curl -X POST http://localhost:3000/api/mcp/context \
-H "Content-Type: application/json" \
-H "X-API-Key: your-api-key" \
-d '{
"query": "add an API endpoint",
"repo_id": "your-repo-id"
}'
π Project Structure
src/
βββ app/ # Next.js App Router
β βββ api/ # API Routes
β β βββ auth/ # NextAuth endpoints
β β βββ github/ # GitHub API proxy
β β βββ mcp/ # MCP context & health
β β βββ patterns/ # Pattern queries
β β βββ repos/ # Repository CRUD
β β βββ webhooks/ # GitHub webhooks
β βββ dashboard/ # Dashboard pages
β βββ onboarding/ # Onboarding flow
βββ components/ # React components
β βββ ui/ # shadcn/ui components
β βββ dashboard/ # Dashboard-specific
βββ lib/ # Core libraries
βββ db/ # Database client & schema
βββ github/ # GitHub API client
βββ indexing/ # AST parser & queue
βββ mcp/ # MCP server & context generator
βββ patterns/ # 8 pattern detectors
βββ utils/ # Types, helpers, Groq client
π Pattern Types
Rules-Based (No API Calls)
| Pattern | What It Detects |
|---|---|
| Error Handling | try-catch blocks, wrapper functions (handleError, etc.) |
| Import Style | Relative (./path), Absolute (@/, ~/), Barrel exports |
| Naming Convention | camelCase, snake_case, PascalCase |
| File Structure | App Router, Pages Router, Components directory |
Hybrid (Rules + LLM Fallback)
| Pattern | What It Detects |
|---|---|
| API Format | Next.js API Routes, response structure patterns |
| Validation | Zod, Yup, Joi, Valibot, custom validation |
| Database | Prisma, Drizzle, TypeORM, Mongoose, Supabase, Kysely |
| Authentication | NextAuth, Clerk, Auth0, Supabase Auth, Firebase |
π§ Troubleshooting
<details> <summary><strong>Database connection failed</strong></summary>
- Ensure your Supabase project is active
- Check if the password contains special characters (URL-encode them)
- Use port
5432for direct connection,6543for pooled
</details>
<details> <summary><strong>GitHub OAuth redirect error</strong></summary>
- Verify callback URL is set to
http://localhost:3000/api/auth/callback/github - Ensure
NEXTAUTH_URLmatches your app URL
</details>
<details> <summary><strong>Pattern detection returns empty</strong></summary>
- Check if repository indexing is complete (status: "completed")
- Verify there are TypeScript/JavaScript files in the repo
- Check Redis queue for pending jobs
</details>
<details> <summary><strong>MCP not connecting to Cursor</strong></summary>
- Restart Cursor after updating
mcp.json - Check API key is valid and not expired
- Verify the repo_id matches a indexed repository
</details>
πΊοΈ Roadmap
- [ ] Multi-language support β Python, Go, Rust
- [ ] Custom pattern definitions β User-defined pattern rules
- [ ] Team collaboration β Shared pattern configs
- [ ] VS Code extension β Native VS Code integration
- [ ] Pattern analytics β Usage trends and insights
π€ Contributing
We welcome contributions! See CONTRIBUTING.md for guidelines.
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
π License
This project is licensed under the MIT License - see the LICENSE file for details.
<div align="center">
Built with β€οΈ for the AI-assisted coding community
β Star this repo if you find it useful!
</div>
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.