search_conversationsLABSCO SUMMARY
The answer you half-remember is in a conversation from three weeks ago.
It is built around not flooding the context: search returns snippets, conversations are fetched in parts, and scope is limited before results come back. The command search is the sharpest of them - the invocation you used once and never wrote down, found by what it did rather than by its name.
What it is
A search server over two local stores: Memex's conversation history and the project directories in your workspace. It returns targeted snippets and scoped results rather than whole files.
What you get
- Conversation search by text, metadata and filters, with relevance scoring
- A specific part of a conversation, retrieved without pulling the whole thing into context
- Project search by content, file type and name
- A project summary with the technologies it detects
- Commands, CLI usage and code snippets found in past conversations, filtered by the kind of command you mean
- Faceted filtering on dates, projects and file types
Requirements
A local Memex install - the server reads the history directory under Application Support and the projects in your workspace folder, both at fixed paths. Node, and a build from the repository.
Setup effort
Build from source — git clone https://github.com/memextech/memex-targeted-search-server.git
USE CASES
01
Recovering a command you ran once and never wrote down
Describe what it did rather than how it was spelled, then read the surrounding exchange to get the arguments right.
02
Finding the conversation where you solved this before
Search history by text and date, then pull only the part of the thread that matters instead of the whole transcript.
03
Locating which project a piece of code lives in
Search the workspace by content and file type, then read the summary of whichever project it turned up in.
04
Getting reacquainted with an old project
Start from the overview and its detected technologies, then search inside it for the parts you need to touch.
5 tools
Listed in project docs. Your client may show a different list.
get_conversation_snippetsearch_projectsget_project_overviewfind_commandBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
# Clone the repository
git clone https://github.com/memextech/memex-targeted-search-server.git
cd memex-targeted-search-server
# Install dependencies
npm install
# Build the project
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"memex-search": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MEMEX_TARGETED_SEARCH_SERVER>/dist/index.js"
]
}
}
}
