Claude Server MCP
Claude Server is an MCP implementation that enhances Claude's capabilities by providing sophisticated context management across sessions, enabling persistent knowledge organization through hierarchical project contexts and continuous conversation threads stored in a well-structured ~/.claude directory.
What is Claude Server?
Claude Server is a Model Context Protocol (MCP) server that enhances Claude's capabilities by enabling sophisticated context management across sessions and allowing for persistent knowledge organization through hierarchical project contexts and continuous conversation threads.
How to use Claude Server?
The server is automatically configured in your Claude desktop app's MCP settings, storing all contexts in the '~/.claude/' directory for better organization. Users can save project and conversation contexts through provided TypeScript tools.
Key features of Claude Server?
- Project context management with hierarchical organization and parent-child relationships.
- Conversation continuity allowing for session-based context tracking and metadata-rich storage.
- Efficient storage system with JSON-based storage and quick lookup indexing.
Use cases of Claude Server?
- Managing complex project contexts for software development.
- Maintaining continuity in conversations for client discussions.
- Organizing contextual metadata for various organizational projects.
FAQ from Claude Server?
- Is Claude Server easy to integrate?
Yes, it integrates seamlessly with the Claude desktop app and is automatically configured.
- Can I customize the context storage location?
The default storage location is '~/.claude/', but it can be configured in the settings as needed.
- What kind of metadata can be stored?
Users can store various project-specific metadata such as status, references, and tags along with content.
Claude Server MCP
A Model Context Protocol (MCP) server that provides sophisticated context management capabilities for Claude, enabling persistent context across sessions, project-specific context organization, and conversation continuity.
Features
-
Project Context Management
- Hierarchical context organization
- Parent-child relationships
- Cross-referencing between contexts
- Project-specific metadata
-
Conversation Continuity
- Session-based context tracking
- Conversation chaining
- Metadata-rich context storage
- Flexible tagging system
-
Efficient Storage
- Organized directory structure
- JSON-based storage
- Quick lookup indexing
- Asynchronous operations
Installation
The server is automatically configured in your Claude desktop app's MCP settings. All contexts are stored in ~/.claude/ for better organization:
~/.claude/
├── contexts/ # General conversation contexts
├── projects/ # Project-specific contexts
└── context-index.json # Quick lookup index
Tools
Project Context Management
// 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" }
}
});
Conversation Management
// 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"]
}
});
Context Retrieval
// Get context
use_mcp_tool({
server_name: "claude-server",
tool_name: "get_context",
arguments: {
id: "feature-design-v1",
projectId: "my-project"
}
});
// List contexts
use_mcp_tool({
server_name: "claude-server",
tool_name: "list_contexts",
arguments: {
projectId: "my-project",
tag: "design",
type: "project"
}
});
Documentation
- Context Management Guide - Detailed guide on context types and usage
- Architecture Overview - Technical implementation details
- Usage Guide - General usage instructions
- Claude Desktop Integration - Integration with Claude Desktop
Development
- Clone the repository
- Install dependencies:
npm install - Build the server:
npm run build - The server will be built to
build/index.js
Configuration
The server is configured through the Claude desktop app's configuration file at:
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"claude-server": {
"command": "node",
"args": ["/path/to/claude-server/build/index.js"]
}
}
}
Contributing
Contributions are welcome! Please feel free to submit issues and pull requests.
License
MIT
