- Home
- MCP servers
- Context Manager
Context Manager
- typescript
8
GitHub Stars
typescript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"tejpalvirk-contextmanager": {
"command": "npx",
"args": [
"-y",
"github:tejpalvirk/contextmanager"
]
}
}
}You manage persistent, cross-domain AI context with a centralized MCP Context Manager. It orchestrates domain-specific MCP servers so you can build, load, and relate knowledge across projects, students, research domains, and more, while keeping context efficiently accessible for your AI models.
How to use
Use the MCP Context Manager to interact with domain-specific MCP servers through a single interface. Start a session to review past work, build and load context for entities like projects or studies, and create relationships that connect ideas across domains. You can also set an active domain to focus on a particular context before performing actions.
How to install
Prerequisites: Node.js v16 or higher and npm installed on your system.
Step by step commands to install and run the MCP Context Manager and its domain servers.
# Install Node.js and npm if you do not have them yet, then proceed with these steps
npm install -g npm
# Run the Context Manager directly (recommended)
npx github:tejpalvirk/contextmanager
# Alternatively install globally and run a specific server command
npm install -g github:tejpalvirk/contextmanager
# Start the context manager and expose domain servers
mcp-server-contextmanager
# Run a specific domain server directly (examples)
contextmanager-developer
contextmanager-project
contextmanager-student
contextmanager-qualitativeresearch
contextmanager-quantitativeresearch
# If you prefer building from source for customization
git clone https://github.com/tejpalvirk/contextmanager.git
cd contextmanager
npm install
npm run build
node main/index.js
"}]},{
Environment and runtime notes: You may adjust memory and log settings with command-line options when starting the manager. If you need to point domain servers to specific storage paths, configure MEMORY_FILE_PATH and SESSIONS_FILE_PATH as shown in environment examples.
Configuration and usage notes
Domain handling is centralized: a domain management tool lets you switch the active domain so actions apply to the correct knowledge graph. Session management provides quick overviews of past work and enables future improvements to the knowledge graph after each session.
Cross-domain work is supported. You can create relationships between entities across domains to model dependencies, ownership, or collaboration across contexts.
Troubleshooting
Port conflicts, connection refusals, or missing domain servers are common issues. Verify that the MCP Context Manager and all domain servers are running on the expected ports. If a specific domain server is not found, ensure the domain name is correct and registered with the Context Manager.
For path or module errors, confirm all domains’ memory and sessions file paths are valid and accessible. If a method is not found for a domain, confirm that the domain supports the requested operation.
Example workflow
// Set the active domain to developer
setActiveDomain(domain="developer")
// Start a new session
startsession(domain="developer")
// Create a new project entity
buildcontext(type="entities", data={
"entityType": "project",
"name": "MyProject",
"description": "A sample project",
"language": "TypeScript",
"framework": "React"
})
// Load context for the project
loadcontext(entityName="MyProject", entityType="project")
// Create a component for the project and set its status to active
buildcontext(type="entities", data={
"entityType": "component",
"name": "AuthService",
"project": "MyProject",
"description": "Authentication service component",
"dependencies": ["UserService"]
})
buildcontext(type="relations", data=[
{ from: "AuthService", to: "active", relationType: "has_status" },
{ from: "AuthService", to: "high", relationType: "has_priority" }
])
Cross-Domain Operations
Create relationships between entities in different domains to model ownership or coordination across knowledge graphs.
Available tools
startsession
Start a new session for the active domain and review past work.
endsession
End the current session and update the knowledge graph for future sessions.
buildcontext
Create or update context such as entities, relations, and status/priority for domain-specific graphs.
loadcontext
Load context data for a specific entity into your current working context.
deletecontext
Remove context data for specified entities or relations.
setActiveDomain
Switch the active domain to target a specific domain MCP server.
relateCrossDomain
Create relationships across entities from different domains to model cross-domain connections.