Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Memex Targeted Search Serverfind the command I used to run the memex agent cli"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Memex Targeted Search Server
A Model Context Protocol (MCP) server that provides targeted search capabilities across Memex conversation history and project files.
Overview
This MCP server enables AI agents to efficiently search through:
Conversation History: 952+ conversation files from Memex with metadata, titles, summaries, and message content
Project Files: 516+ project directories in the user's workspace with various file types and technologies
Features
š Core Search Tools
search_conversations- Search conversation history by text, metadata, and filtersget_conversation_snippet- Retrieve specific parts of conversations without context overloadsearch_projects- Search project files by content, file types, and namesget_project_overview- Get project summaries with technology detectionfind_command- NEW! Find specific commands, CLI usage, or code snippets from conversation history
šÆ Smart Context Management
Returns targeted snippets instead of full conversations
Limits search scope to prevent context explosion
Supports faceted filtering (dates, projects, file types)
Provides relevance scoring for search results
Installation
Configuration
The server is configured to search:
Conversation History:
~/Library/Application Support/Memex/history/Project Files:
~/Workspace/
MCP Server Configuration
Add to your MCP configuration (e.g., Claude Desktop config):
Usage Examples
1. Find Forgotten Commands
"I don't remember what the command is to run the memex agent cli"
Find specific npm commands
Example Response:
2. Search Conversations
Find conversations about specific topics
Example Response:
Filter by date range and project
3. Get Conversation Details
Retrieve specific messages from a conversation
Example Response:
4. Search Projects
Find files by technology
Search all project files
Example Response:
5. Get Project Overview
Analyze project structure and tech stack
Example Response:
Real-World Usage Scenarios
Scenario 1: "I forgot that command..."
Scenario 2: Finding Related Work
Scenario 3: Code Reference Lookup
Scenario 4: Cross-Reference Discovery
API Reference
search_conversations
Purpose: Search conversation history with flexible filtering
Parameters:
query(required),limit,project,date_from,date_toReturns: Array of conversation metadata with relevance scoring
get_conversation_snippet
Purpose: Retrieve specific message ranges from conversations
Parameters:
conversation_id(required),message_start,message_countReturns: Conversation snippet with message details
search_projects
Purpose: Search project files by content and metadata
Parameters:
query(required),file_types,limitReturns: Array of file matches with context
get_project_overview
Purpose: Analyze project structure and technology stack
Parameters:
project_name(required)Returns: Project summary with file counts and tech detection
find_command
Purpose: Find specific commands, CLI usage, or code snippets from conversation history
Parameters:
query(required),command_type(cli/code/config/any),limitReturns: Array of commands with context, confidence scoring, and conversation references
Architecture
Built with:
TypeScript - Type-safe development
MCP SDK - Official Model Context Protocol SDK
Node.js - Runtime environment
File System APIs - Direct file access for performance
Performance Considerations
Limits search scope to prevent overwhelming results
Uses streaming JSON parsing for large files
Implements intelligent file filtering
Caches frequently accessed metadata
Returns truncated content with full context available on demand
Agent Experience
The server is designed for optimal agent interaction:
Targeted Search: Find specific information without context overload
Faceted Filtering: Multiple search dimensions (date, project, file type)
Progressive Discovery: Start with summaries, drill down to details
Context Preservation: Maintain conversation and project relationships
Development
Running in Development
Building for Production
Testing
The server includes comprehensive error handling and graceful degradation for:
Missing or corrupted conversation files
Inaccessible project directories
Invalid JSON parsing
Large file handling
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
ISC License
š¤ Generated with Memex
Co-Authored-By: Memex noreply@memex.tech