MCP.so
Sign In

Developer MCP Server

@tejpalvirk

About Developer MCP Server

MCP server to help developers manage project context across sessions

Basic information

Category

Developer Tools

Runtime

node

Transports

stdio

Publisher

tejpalvirk

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "developer": {
      "command": "npx",
      "args": [
        "-y",
        "github:tejpalvirk/developer"
      ]
    }
  }
}

Tools

6

Starts a new development session and provides information about recent sessions, active projects, high-priority tasks, and upcoming milestones.

Loads detailed context for an entity (project, component, feature, task, etc.) and tracks this context loading as part of the current session.

Performs a structured analysis of the development session through multiple stages (summary, achievements, task updates, new tasks, project status) and records this information in the persistent knowledge graph.

Creates new entities, relations, or observations in the knowledge graph.

Removes entities, relations, or observations from the knowledge graph.

Retrieves information from the knowledge graph with different query types (graph, search, nodes, related, decisions, milestone).

Overview

What is Developer MCP Server?

A context management system for software development teams that maintains persistent context across coding sessions, tracking project structure, dependencies, and progress. It is designed for software development teams.

How to use Developer MCP Server?

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.

Key features of Developer MCP Server

  • 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.

Use cases of Developer MCP Server

  • Resume work with full context from previous session.
  • Onboard new developers by showing project architecture.
  • Record session achievements and task updates.
  • Retrieve architectural decision rationale.
  • Analyze impact of changes on dependencies.
  • Track project progress toward milestones.

FAQ from Developer MCP Server

What data does Developer MCP Server persist?

It persists a knowledge graph of entities (projects, components, features, etc.) and their relationships, plus session data. Storage paths are configurable via environment variables.

How is Developer MCP Server installed?

It can be run via npx from GitHub, installed globally via npm, or used as a Docker container. Configuration for Claude Desktop is provided.

What are the runtime requirements?

Node.js is required for the npm-based installation. Docker is required for the Docker method. No other dependencies are mentioned.

Where is data stored?

Data is stored in files specified by MEMORY_FILE_PATH (default ./developer/memory.json) and SESSIONS_FILE_PATH (default ./developer/sessions.json). Paths can be absolute or relative.

What transport/auth does it use?

The README does not mention transport or authentication. It is designed for use with MCP clients like Claude Desktop, presumably using stdio transport.

Comments

More Developer Tools MCP servers