This MCP server provides a sophisticated context management system for Claude, allowing you to organize and maintain persistent contexts across sessions with features like hierarchical organization, session tracking, and metadata-rich storage.
The Claude Server MCP is automatically configured in your Claude desktop app's MCP settings. All contexts are stored in the ~/.claude/
directory with the following structure:
~/.claude/
├── contexts/ # General conversation contexts
├── projects/ # Project-specific contexts
└── context-index.json # Quick lookup index
To manually configure the server in your Claude desktop app, modify the configuration file located at:
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"claude-server": {
"command": "node",
"args": ["/path/to/claude-server/build/index.js"]
}
}
}
You can save project-specific contexts with parent-child relationships, references, tags and metadata:
// Save project context
use_mcp_tool({
server_name: "claude-server",
tool_name: "save_project_context",
arguments: {
id: "feature-design-v1",
projectId: "my-project",
content: "Design discussion...",
parentContextId: "requirements-v1",
references: ["api-spec-v1"],
tags: ["design"],
metadata: { status: "in-progress" }
}
});
Create and link conversation contexts with session tracking:
// Save conversation context
use_mcp_tool({
server_name: "claude-server",
tool_name: "save_conversation_context",
arguments: {
id: "chat-2024-01-01",
sessionId: "session-123",
content: "Discussion content...",
continuationOf: "previous-chat-id",
tags: ["meeting"]
}
});
You can retrieve specific contexts or list multiple contexts:
// Get a specific context
use_mcp_tool({
server_name: "claude-server",
tool_name: "get_context",
arguments: {
id: "feature-design-v1",
projectId: "my-project"
}
});
// List contexts with filters
use_mcp_tool({
server_name: "claude-server",
tool_name: "list_contexts",
arguments: {
projectId: "my-project",
tag: "design",
type: "project"
}
});
For more detailed information about using the server, refer to the documentation in the project repository.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "claude-server" '{"command":"node","args":["/path/to/claude-server/build/index.js"]}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"claude-server": {
"command": "node",
"args": [
"/path/to/claude-server/build/index.js"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"claude-server": {
"command": "node",
"args": [
"/path/to/claude-server/build/index.js"
]
}
}
}
3. Restart Claude Desktop for the changes to take effect