How to Search Inside Saved Outlook Emails (.msg and .eml) Offline — and Let an AI Read the Whole Thread
A lot of important email doesn't live in a mailbox any more. It lives in a project folder: a contract thread someone dragged out of Outlook, a client's .eml forwarded from a different system, last year's approvals saved next to the documents they approve. Your mail client's search does not look in those folders, and File Explorer usually only sees the file names. This post shows how to search the text of those files offline, and how an AI assistant can rebuild the conversation they belong to.
Which email files can LocalSynapse search?
- .msg — Outlook's single-message format, including older messages stored in legacy Korean or Japanese encodings.
- .eml — the standard internet message format that most mail programs can export.
The message text is indexed alongside your Word, Excel, PowerPoint, PDF, HWP and text files, so a single search covers a contract and the email that discussed it. Results for emails show the sender and the send date. If a message has no Date header, the file's last-modified time is used instead, so it still has a usable date.
How do I make saved Outlook email searchable?
- Save the messages as files. In classic Outlook for Windows you can save a message as a .msg file (File > Save As), or drag it into a File Explorer folder.
- Keep them in a folder LocalSynapse indexes. A project folder is fine; the emails sit next to the documents they refer to.
- Search by what you remember. A phrase, a topic, or a figure from the message body. With the optional AI model installed (about 2.3 GB), you can also search by meaning — "the delay on the second shipment" can find a message that says "batch two will be late".
How can an AI assistant read the whole thread?
With LocalSynapse's MCP server connected to Claude Desktop or another MCP client (setup guide), two tools work together:
search_filesfinds the message by its content. Each email result includes anemailId, thesenderandsentAt.get_email_threadtakes thatemailId(or an internet Message-ID) and returns the full thread: parent messages found by followingIn-Reply-Toupward, follow-up replies found by following it downward, oldest first, capped at 200 messages.
So you can ask "Find the thread where the supplier agreed to the new delivery date and summarise who committed to what". The assistant searches, picks the message, reads the thread in order, and answers from what was actually written. For a wider view, get_timeline lists file changes and email arrivals in a date range together.
When does a thread not link up?
Thread linking depends on the Message-ID and In-Reply-To headers inside each message. A .msg file saved without its internet headers has neither, so it can still be found by search but cannot be connected to its parent or replies. The thread is only as complete as the set of messages you have saved: a reply that exists only in someone's mailbox is not on your disk.
What LocalSynapse does not do
- It doesn't read Outlook mailbox data files (.pst, .ost) or connect to your mail server. It works on saved .msg and .eml files.
- It doesn't search inside attachments embedded in a message. They are recorded by name, type and size. Save an attachment as its own file to search inside it.
- It skips messages it cannot open, such as encrypted .msg files or files that are damaged.
- It doesn't index cloud-only placeholder files. Files that are only in OneDrive or similar must be stored on the PC first.
- Windows and macOS only, on the CPU. The Windows build is not code-signed; the macOS builds are not signed by Apple.
- Privacy has one boundary. Your files are not uploaded, but messages an assistant reads through MCP become part of that conversation. See the privacy page.