Run Adeu on a local LLM: contract redlining and email, fully self-hosted

Legal documents are about as sensitive as data gets. Plenty of teams would rather not send contracts to a hosted model at all. So we made sure Adeu runs wherever your model runs, including entirely on your own machine.

Adeu ships as a standard Model Context Protocol server. Any MCP-capable client can connect to it, which means any local LLM setup that speaks MCP can drive Adeu's contract and email tools. In the walkthrough below we use Unsloth, but the same steps apply to Claude Desktop, Cursor, Windsurf, or any other MCP client running a local model.

What the video shows

Running against a local Qwen3.6-35B-A3B-MTP-GGUF model in Unsloth, with no cloud model in the loop, Adeu:

• Logs in to Adeu Cloud from inside the chat
• Searches and fetches emails from the connected inbox
• Drafts a reply into the native draft box
• Opens a local Word document by file path
• Makes tracked-changes edits to that document on disk

The model doing the reasoning is local. Adeu is the toolbox it reaches for.

Setup, start to finish

01Load your local model in Unsloth

Download and load a model through the Unsloth UI. In the video we use Qwen3.6-35B-A3B-MTP-GGUF, already downloaded, but any model your hardware can run will do. Once it loads, you have a working local chat.

02Allow local MCP servers

Unsloth gates local (stdio) MCP servers behind an environment variable. Set it before launching:

• UNSLOTH_STUDIO_ALLOW_STDIO_MCP=1

Without this, Unsloth will not start a local command-based MCP server, and Adeu will not appear.

03Add the Adeu MCP server

In Unsloth's MCP settings, add Adeu using the install command:

• npx -y @adeu/mcp-server

That is the whole install. The command pulls and runs the Node build of Adeu's engine, so you do not need Python or a separate service. Node is the only prerequisite.

04Start working

Reconnect the server in the UI and the tools show up in chat. Point Adeu at a contract on disk and ask for a review, or ask it to summarize a thread and draft a reply. The model plans the work; Adeu reads and writes the documents.

What runs locally, and what needs the cloud

This is worth being precise about.

Local, no account required. Reading and editing .docx files works entirely on your machine. Give Adeu a file path, and it reads the document, applies native Word tracked changes, and writes the result back. Nothing leaves your disk, and the model stays local. This is the open-source engine, free to use.

Cloud, gated behind a call. The email tools shown in the video, searching an inbox, fetching messages, and drafting replies, run through Adeu Cloud and need an authenticated session. Adeu Cloud connects to both Google and Microsoft, and it is not limited to one account: you can link multiple inboxes across providers, including shared and delegated mailboxes, and manage all of them from the same chat. Attachments are handled end to end, so Adeu can pull a contract off an incoming message, work on it, and send a reply with the revised document attached. We set these accounts up during onboarding rather than self-serve, so if you want the email side, book a call.

Where this gets useful is when the two halves meet. The DOCX engine is local and free: hand it a contract on disk and get back a clean tracked-changes redline. Add Adeu Cloud on top, and a lawyer can pull a counterparty's draft straight out of Gmail or Outlook, redline it, and send the marked-up file back as an attachment, all from one conversation. Local review, real inboxes, one workflow.

Why this matters

You keep control of the model and the data. The contract never has to touch a hosted LLM. And because Adeu is just an MCP server, you are not locked into one client or one model: swap the local model, swap the client, and the same contract and email tools come with you.

The redlining engine is open source. Read the code, audit it, and run it yourself at github.com/dealfluence/adeu.

Related articles