email_searchLABSCO SUMMARY
One tool, because the work happens upstream.
The interesting engineering is not in this server — it is in the capture filters and the email-shaped vector index behind it, and what reaches the model is a single search call over the result. That is the right split for mail: the assistant never holds the archive, so the size of the mailbox stops being the limit. It only makes sense if your organisation already runs Mail2Cloud Advanced; the demo accounts exist for looking before you commit.
What it is
A Go client for mxHERO Mail2Cloud Advanced, a service that captures mail from one or more company accounts through filters, optimises it and stores it in an isolated tenant of a vector database built for email search. This server queries that tenant. Results come back with secure links to the original messages, which survive a user deleting their copy.
What you get
email_searchtakes a query string and returns JSON search results across every captured account- Secure links back to the original emails in the results
- Search over repositories far larger than a model's context window, because the retrieval happens in the vector store
- A native static binary — once compiled for your OS and CPU there are no runtime dependencies to install
Requirements
An mxHERO Vector Search token; personal access tokens are issued at https://lab4-mcp.mxhero.com/tokens, and using the hosted service needs an account. Go 1.22 or higher to build — go mod tidy then a make target for your platform, which drops a binary in bin. Configure your client with the full path to the binary and pass the token as -t. Prebuilt binaries and signed installers are in the repository. This repo is the stdio build; a Streamable HTTP endpoint and a Python version exist separately.
Setup effort
Build from source — git clone https://github.com/mxaiorg/mxmcp
USE CASES
01
Finding a thread nobody can remember the subject of
Search across every captured account at once and follow the link to the original.
02
Pulling the history on a customer or a deal
Query the archive for everything related and let the model summarise it.
03
Recovering context after someone deletes their mailbox copy
Search the captured archive, which holds its own copy of the message.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
Go 1.22 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/mxaiorg/mxmcp
cd mxmcp
go mod tidyCompile for the target OS/arch, e.g. make mac-arm (also windows-intel / mac-intel / linux-intel); output lands in bin/
Copy the binary somewhere you have permission to run it, for example your home directory:
TERMINAL
cp bin/mxmcp-mac-arm ~/Ensure it is executable, e.g. chmod 755 ~/mxmcp-mac-arm
Add the mcpServers block to claude_desktop_config.json with the full binary path and your -t token
Restart Claude if it is running
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"mxhero-mcp-server": {
"command": "<YOUR_FULL_PATH_TO_MXMCP>",
"args": [
"-t",
"<YOUR_TOKEN>",
"-d",
"<YOUR_OPTIONAL_CUSTOM_TOOL_DESCRIPTION>"
]
}
}
}
