MCP Search: Date filters (dateStart/dateEnd) don't work correctly #241

New issue

Closed

opened 2026-01-25 00:34:22 +00:00 by jack · 0 comments

jack commented

2026-01-25 00:34:22 +00:00

Owner

Problem

When using the MCP search tool with dateStart and dateEnd parameters, the results don't respect the date range and return observations from outside the specified period.

Example:

mcp__plugin_claude-mem_mcp-search__search({
  query: "task repository migration",
  dateStart: "2026-01-24T00:00:00Z",
  dateEnd: "2026-01-24T23:59:59Z",
  limit: 30
})

Result: Returns observations from 2026-01-23 and 2026-01-21, not from 2026-01-24.

Expected Behavior

Search should only return observations where created_at falls within the specified date range.

Investigation Needed

Check if the date parameters are being passed to the search query
Verify the SQL query includes the date filter conditions
Check if there's a timezone conversion issue

## Problem When using the MCP search tool with `dateStart` and `dateEnd` parameters, the results don't respect the date range and return observations from outside the specified period. **Example:** ```typescript mcp__plugin_claude-mem_mcp-search__search({ query: "task repository migration", dateStart: "2026-01-24T00:00:00Z", dateEnd: "2026-01-24T23:59:59Z", limit: 30 }) ``` **Result:** Returns observations from 2026-01-23 and 2026-01-21, not from 2026-01-24. ## Expected Behavior Search should only return observations where `created_at` falls within the specified date range. ## Investigation Needed 1. Check if the date parameters are being passed to the search query 2. Verify the SQL query includes the date filter conditions 3. Check if there's a timezone conversion issue