fix: rename 'mem-search' to 'mcp-search' for consistency across documentation and configuration

This commit is contained in:
Alex Newman
2025-12-28 22:55:05 -05:00
parent b92eb3dbb5
commit d7c183b3e1
5 changed files with 34 additions and 7 deletions
+4 -4
View File
@@ -17,7 +17,7 @@ Claude Desktop can access your claude-mem memory database through the **mem-sear
Before installing the skill, ensure:
1. **claude-mem is installed** and the worker service is running
2. **MCP server is configured** in Claude Desktop (the skill uses the `mem-search` MCP server)
2. **MCP server is configured** in Claude Desktop (the skill uses the `mcp-search` MCP server)
### Verify Worker is Running
@@ -52,7 +52,7 @@ npm run build # Generates plugin/skills/mem-search.zip
### Step 3: Configure MCP Server
The skill requires the `mem-search` MCP server. Add this to your Claude Desktop configuration:
The skill requires the `mcp-search` MCP server. Add this to your Claude Desktop configuration:
<Tabs>
<Tab title="macOS">
@@ -61,7 +61,7 @@ The skill requires the `mem-search` MCP server. Add this to your Claude Desktop
```json
{
"mcpServers": {
"mem-search": {
"mcp-search": {
"command": "node",
"args": [
"/Users/YOUR_USERNAME/.claude/plugins/marketplaces/thedotmack/plugin/scripts/mcp-server.cjs"
@@ -77,7 +77,7 @@ The skill requires the `mem-search` MCP server. Add this to your Claude Desktop
```json
{
"mcpServers": {
"mem-search": {
"mcp-search": {
"command": "node",
"args": [
"C:\\Users\\YOUR_USERNAME\\.claude\\plugins\\marketplaces\\thedotmack\\plugin\\scripts\\mcp-server.cjs"
+1 -1
View File
@@ -1,6 +1,6 @@
{
"mcpServers": {
"mem-search": {
"mcp-search": {
"type": "stdio",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/mcp-server.cjs"
}
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "claude-mem-plugin",
"version": "8.2.5",
"version": "8.2.6",
"private": true,
"description": "Runtime dependencies for claude-mem bundled hooks",
"type": "module",
+27
View File
@@ -3,6 +3,33 @@ name: mem-search
description: Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.
---
<!-- TL;DR - Essential Workflow -->
## Quick Reference
**The 3-Layer Pattern (ALWAYS follow this):**
1. **Search** - Get index of results with IDs
```
search(query="...", limit=20, project="...")
```
Returns: Table with IDs, titles, dates (~50-100 tokens/result)
2. **Timeline** - Get context around interesting results
```
timeline(anchor=<ID>, depth_before=3, depth_after=3, project="...")
```
Returns: Chronological context showing what was happening
3. **Fetch** - Get full details ONLY for relevant IDs
```
get_observations(ids=[...]) # ALWAYS batch for 2+ items
```
Returns: Complete details (~500-1000 tokens/result)
**Why:** 10x token savings. Never fetch full details without filtering first.
---
# Memory Search
Search past work across all sessions. Simple workflow: search → get IDs → fetch details by ID.
+1 -1
View File
@@ -435,7 +435,7 @@ const tools = [
// Create the MCP server
const server = new Server(
{
name: 'mem-search-server',
name: 'mcp-search-server',
version: '1.0.0',
},
{