Launching today
Search Stack
Managed search API your AI agent can run end-to-end
7 followers
Managed search API your AI agent can run end-to-end
7 followers
Full-text, vector, geo, and image search over one JSON API — with typeahead, a drop-in autocomplete widget, and official TypeScript/.NET clients. What makes it different: the entire index is controllable via MCP (read and write, not just querying), so an AI agent can create lists, add records, and tune search for you. And built-in evaluations let you prove a relevance change is actually better before you ship it. Lucene-backed, no cluster to babysit.
How does the MCP read/write access work in practice when an agent makes changes — is there version history or some way to roll back if an automated tweak tanks relevance on a key query?
How does the MCP write access handle conflicts if my agent and a teammate are both updating records at the same time, and is there any audit trail to see what changed?