Developer MCP Server
About
A context management system designed for software development teams with customizable data storage.
Details
- Author
- tejpalvirk
- GitHub stars
- 5
- Downloads
- 208
- Categories
- Developer Tools, Project Management, Knowledge Base, Automation
Jump to
- Persistent development context across sessions.
- Session management with structured recording.
- Dependency tracking between components, features, technologies.
- Project status insights for components, features, issues, milestones.
- Component context retrieval with dependencies and related issues.
- Decision history tracking for architectural decisions.
- Milestone progress tracking to identify bottlenecks.
- Related entity discovery for complete context.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Developer MCP ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install via npm (npx github:tejpalvirk/developer), global install (npm install -g github:tejpalvirk/contextmanager/developer), or Docker. Configure in Claude Desktop via claude_desktop_config.json. Use environment variables MEMORY_FILE_PATH and SESSIONS_FILE_PATH to customize data storage. Invoke tools like startsession, loadcontext, endsession, buildcontext, deletecontext, advancedcontext.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"developer mcp server": {
"developer": {
"command": "npx",
"args": [
"-y",
"github:tejpalvirk/developer"
]
}
}
}
}McpServers
{
"developer": {
"command": "npx",
"args": [
"-y",
"github:tejpalvirk/developer"
]
}
}Developer MCP Server
Context management system designed for software development teams. The Developer MCP Server maintains persistent context across coding sessions, ensuring you never lose track of the project's structure, dependencies, and progress.
<a href="https://glama.ai/mcp/servers/@tejpalvirk/developer">
</a>
Features
- Persistent Development Context: Pick up exactly where you left off in your last session, with complete context about the components, issues, and tasks you were working on.
- Session Management: Start new development sessions and record your achievements, task updates, and project status changes when you finish, creating a persistent record of your development activities.
- Dependency Tracking: Understand how components, features, and technologies relate to each other with a comprehensive dependency model.
- Project Status Insights: Get immediate visibility into project progress, including status of components, features, issues, and milestones.
- Component Context Retrieval: Understand any component's purpose, implementation details, dependencies, and related issues at a glance.
- Decision History: Track why architectural and implementation decisions were made, when, and by whom—no more guessing why something was built a certain way.
- Milestone Progress Tracking: Monitor progress toward project milestones and identify potential bottlenecks before they derail your timeline.
- Related Entity Discovery: Quickly find all related entities for any component, feature, or task to understand its complete context.
Entities
The Developer MCP Server recognizes the following types of entities in your software development context:
- Project: Overall software project or product
- Component: Module, service, package, or logical unit within a project
- Feature: Specific functionality being developed
- Issue: Bug, problem, or defect to be addressed
- Task: Work item or activity needed for development
- Developer: Team member working on the project
- Technology: Programming language, framework, library, or tool
- Decision: Important technical or architectural decision
- Milestone: Key project deadline or phase
- Environment: Development, staging, or production environment
- Documentation: Project documentation resource
- Requirement: Project requirement or specification
Relationships
The Developer MCP Server models the following relationships between entities, mirroring real-world software development dynamics:
- depends_on: Entity A requires Entity B to function
- implements: Component implements a feature
- assigned_to: Task is assigned to a developer
- blocked_by: Task is blocked by an issue
- uses: Component uses a technology
- part_of: Component is part of a project
- contains: Project contains a component
- works_on: Developer works on a project/component
- related_to: General relationship between entities
- affects: Issue affects a component
- resolves: Task resolves an issue
- created_by: Entity was created by a developer
- documented_in: Component is documented in documentation
- decided_in: Decision was made in a meeting
- required_by: Feature is required by a requirement
- has_status: Entity has a particular status
- depends_on_milestone: Task depends on reaching a milestone
- precedes: Task precedes another task (sequencing)
- reviews: Developer reviews a component
- tested_in: Component is tested in an environment
Environment Variables
The Developer MCP Server supports the following environment variables to customize where data is stored:
- MEMORY_FILE_PATH: Path where the knowledge graph data will be stored
- Can be absolute or relative (relative paths use current working directory)
- Default: ./developer/memory.json
- SESSIONS_FILE_PATH: Path where session data will be stored
- Can be absolute or relative (relative paths use current working directory)
- Default: ./developer/sessions.json
Example usage:
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
