# MoSearch > MoSearch is an offline-first Windows desktop search tool for local drives and mapped network shares. It includes MoContext, a local Model Context Protocol (MCP) server that lets AI agents retrieve grounded snippets from the MoSearch full-text index, read local files within configured roots, keep lightweight continuity notes, and save/load explicit long-term context digests. ## Primary AI Entry Points - **MoContext MCP endpoint:** `http://127.0.0.1:43210/mcp` - **MoContext REST fallback:** `http://127.0.0.1:43210/v1` - **Scope:** local loopback only; requires MoSearch/MoContext installed, running, and indexed on the user's Windows PC or server. - **MCP discovery:** tools, resources, and resource templates are auto-discovered by MCP clients. Do not hardcode the full tool list when discovery is available. - **Current MCP surface:** tools for server summary, health/capabilities, indexed search, evidence packs, file windows/full-file reads, recent working-set metadata, activity notes, saved packs, context files, guarded memory-file writes, and SaveContext/LoadContext digests. - **External field casing:** MoContext uses `snake_case` for MCP tool schemas, REST JSON/query parameters, JSON resources, and support-report JSON. MCP protocol envelope fields keep their spec-defined casing. ## Recommended AI Startup Flow When MoContext tools/resources are available in an AI client: 1. Call `get_server_summary`. 2. Call `get_capabilities`. 3. Call `get_context_paths` when exact local sys/memory folders are needed. 4. Call `list_context_files` or read `mocontext://context-files` to discover installed docs and durable memory files. 5. Read `mocontext://docs/ai-usage` or call `get_usage_guide` for deeper tool guidance. If MCP is blocked but local HTTP is allowed, use the REST fallback endpoints: `GET /v1/server-summary`, `GET /v1/capabilities`, `GET /v1/context-paths`, `GET /v1/context-files?include_system_docs=true`, and `GET /v1/usage-guide`. Only call `load_context_digest` / `save_context_digest` when the user types `LoadContext`, `LoadContext `, `SaveContext`, or explicitly enables that behavior. Default `LoadContext` returns budget-capped saved digest records plus a compact working-set hint; treat both as orientation and verify source files before claims or code changes. If `truncated` is true, use omitted counts to narrow the query or fetch a specific digest by id. Treat MoContext activity notes and memory files as hints, not source-of-truth. Retrieve fresh evidence from indexed files before making factual claims, design conclusions, or code changes. ## Public Documentation - [MoContext AI Usage Guide](https://meauxsoft.com/MoContext_AI_Usage.md): AI-facing MCP workflow guide, retrieval strategies, memory discipline, and budget reference. - [MoContext Human Guide](https://meauxsoft.com/MoContext_Human.html): human-facing guide with copyable AI custom-instructions text, one-session prompt text, and a technical appendix. - [MoSearch Change Log](https://meauxsoft.com/release-history_MoSearch.json): MoSearch release history. ## Installed Local Files Default install paths vary by version. Common locations: - **MoSearch root:** `C:\Program Files (x86)\Meauxsoft\Mo-Search9.50\` - **MoContext server:** `C:\Program Files (x86)\Meauxsoft\Mo-Search9.50\MoContext\MoContext.Server.exe` - **Product-owned MoContext docs:** `%LOCALAPPDATA%\Meauxsoft\Mo-Search9.50\MoContext\sys\` - **User/AI-owned MoContext memory files:** `%LOCALAPPDATA%\Meauxsoft\Mo-Search9.50\MoContext\memory\` Use `get_context_paths` instead of assuming exact local paths. ## Capabilities - **Local file search:** fast indexing and retrieval of local Windows files. - **Network share support:** indexes mapped network drives configured by the user. - **Grounded AI retrieval:** ranked, budget-capped source/file snippets from the MoSearch full-text index. - **Long-term local context:** installed docs, user/AI-authored Markdown memory files, and SaveContext digest Markdown can be indexed by MoSearch and surfaced through MoContext. - **Offline-first design:** MoContext runs locally; the public website cannot access a user's local MoContext server.