CodeContext
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., "@CodeContextdetect patterns in my team's repository"
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.
π§ CodeContext
AI Coding Context Layer β Make AI assistants understand your team's codebase patterns
Features β’ Quick Start β’ Architecture β’ API Reference β’ Contributing
π― 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.
Related MCP server: My Coding Buddy MCP Server
β¨ 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 install2. Configure Environment
cp .env.example .env.localEdit .env.local with your credentials:
Variable | Description | Where to Get |
| PostgreSQL connection string | Supabase β Settings β Database |
| Redis REST URL | Upstash β Redis β REST API |
| Redis REST token | Same as above |
| Random 32-byte secret | Run: |
| OAuth App client ID | GitHub β OAuth Apps |
| OAuth App secret | Same as above |
| Groq API key |
3. Set Up Database
Run the schema in your Supabase SQL editor:
-- Contents of src/lib/db/schema.sqlOr use the Supabase dashboard to import src/lib/db/schema.sql.
4. Run Development Server
npm run devOpen 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
Ensure your Supabase project is active
Check if the password contains special characters (URL-encode them)
Use port
5432for direct connection,6543for pooled
Verify callback URL is set to
http://localhost:3000/api/auth/callback/githubEnsure
NEXTAUTH_URLmatches your app URL
Check if repository indexing is complete (status: "completed")
Verify there are TypeScript/JavaScript files in the repo
Check Redis queue for pending jobs
Restart Cursor after updating
mcp.jsonCheck API key is valid and not expired
Verify the repo_id matches a indexed repository
πΊοΈ 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.
Built with β€οΈ for the AI-assisted coding community
β Star this repo if you find it useful!
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
- 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/bhasinagam/ContextBridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server