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.

javascript

GitHub Stars

javascript

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": {
    "davidteren-claude-server": {
      "command": "node",
      "args": [
        "/path/to/claude-server/build/index.js"
      ]
    }
  }
}

This MCP server for Claude provides sophisticated context management, enabling persistent context across sessions, project-specific organization, and conversation continuity. It helps you manage project contexts, track conversations, and store metadata-rich context data in a structured, searchable manner.

How to use

You interact with the Claude MCP server through an MCP client. Create and save project contexts to organize design discussions, requirements, and references, and save conversation contexts to preserve session-based dialogue and continuity across chats. Retrieve contexts by id and project, list contexts by project and tag, and leverage the metadata and hierarchical relationships to build structured context trees for your workflows.

Use the MCP client to perform these common actions in your Claude MCP setup:
- Save a project context to capture a design or requirement with a clear parent/child relationship and references.
- Save a conversation context to preserve a chat thread with tags and session linkage.
- Retrieve a specific context by its id and project for quick access.
- List contexts within a project, filtered by tag and type, to survey related materials and keep your workspace organized.

How to install

Prerequisites: ensure you have Node.js installed on your system since the server is configured to run via a local script. Verify you can run node and npm from your terminal.

Step-by-step setup and run flow:

Build and prepare the Claude server MCP components in your development environment (the server is typically wired into Claude Desktop). You will end up with a built index at a path like build/index.js.

Run the local server instance using the provided configuration. The command commonly used is a Node.js invocation pointing to the built entry file, for example:

node /path/to/claude-server/build/index.js

Additional notes

Configuration is managed through Claude Desktop’s MCP settings. Context data is stored under a structured local directory for organization and quick lookup. Note that the project is in active development and is not ready for production use; expect ongoing enhancements to stability, error handling, and security.

Available tools

save_project_context

Saves a project-scoped context with fields such as id, projectId, content, parentContextId, references, tags, and metadata to organize and relate contexts within a project.

save_conversation_context

Saves a conversation context tied to a session, including id, sessionId, content, continuationOf, and tags for ongoing discussions.

get_context

Retrieves a specific context by its id and, if applicable, its projectId.

list_contexts

Lists contexts filtered by projectId, tags, and type to help you browse project or conversation data.

Built by

VeilStrat

AI signals for GTM teams