startsessionLABSCO SUMMARY
The graph is the handover note nobody writes.
The pairing of startsession and endsession is what makes it stick — closing a session is a structured prompt for achievements and task changes, so context that usually evaporates gets written down as a side effect of stopping work. Later, the decision entities answer the question that costs teams the most time: why is it built this way.
What it is
A knowledge graph for software projects, kept between sessions. It models projects, components, features, issues, tasks, developers, technologies, decisions, milestones and environments, and the relationships between them, then serves that back when you start work again.
What you get
- A session opened with recent sessions, active projects, high-priority tasks and upcoming milestones already in front of you (startsession)
- Full context for any entity — a component's purpose, dependencies, related issues and tasks — loaded and recorded as part of the session (loadcontext)
- A structured close: summary, achievements, task status changes, new tasks and project status, written into the graph (endsession)
- Entities, relations and observations created or removed as the project changes (buildcontext, deletecontext)
- Queries over the graph in several forms — the whole graph, search, specific nodes, related entities, decisions, or a milestone's progress (advancedcontext)
- A dependency model that answers what breaks if you change a component, and a decision history recording who decided what and when
Requirements
Node.js. Two file paths hold the graph and the session log; both default inside the working directory and can be pointed elsewhere as environment settings. A container image is also available.
Setup effort
One command — npx -y github:tejpalvirk/developer
USE CASES
01
Resuming after a week away
Open a session and get the components you last touched, their dependencies and the open issues, without reconstructing anything.
02
Recording what you actually did
Close the session and be walked through achievements, task updates and status changes, all written into the graph.
03
Checking what a change would break
Ask for everything that depends on the component before you touch it.
04
Answering why it was built this way
Query the decision entities and the context in which they were made.
05
Bringing a new team member up to speed
Load the project overview — components, relationships and current status — in one pass.
06
Tracking a milestone
Query its tasks and features and see what is at risk before the date arrives.
6 tools
Listed in project docs. Your client may show a different list.
loadcontextendsessionbuildcontextdeletecontextadvancedcontextBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
All 3 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y github:tejpalvirk/developerMCP Clients
Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"developer": {
"command": "npx",
"args": [
"-y",
"github:tejpalvirk/developer"
]
}
}
}Claude Desktop — global install
CLAUDE DESKTOP — GLOBAL INSTALL · JSON
{
"mcpServers": {
"developer": {
"command": "contextmanager-developer"
}
}
}Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"developer": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"mcp/developer"
]
}
}
}
