Team Context MCP Server

Example Use Cases

• 1

  Persistent, shared team context across sessions and projects.

• 2

  Relevant historical bug fixes and architecture decisions injected into prompts.

• 3

  A local, private knowledge base without relying on cloud APIs or vendor lock-in.

Description

This MCP server indexes skills, team knowledge, git history, and cross-project debug memory into local SQLite databases with embeddings, exposing relevant context to any LLM via the MCP protocol. It solves fragmented context issues within sessions, across projects, and team member turnover by maintaining a private, local knowledge base without calling any LLM APIs. The system is LLM-agnostic and supports multiple projects with shared debug memory, ensuring knowledge continuity and zero vendor lock-in.