Mantle

Self-hosted AI memory that every agent and MCP client can tap

Advanced API
Screenshot of Mantle, Self-hosted AI memory that every agent and MCP client can tap

What is Mantle?

Mantle is a self-hosted AI brain that ingests files, mail and notes, builds a layered memory with a knowledge graph, and serves it to Claude, Cursor or any MCP client, with four access tiers and federation between brains.

Mantle is a self-hosted knowledge system built around a single idea: instead of switching to yet another assistant, a person or organisation keeps one brain on their own server and lets every AI client draw from it. Files, mail, voice notes and anything created in the companion app Jackdaw are ingested without tagging or schema work. Facts, entities, links and embeddings are extracted as content arrives, then organised into a layered memory model that runs from persona and journal through conversation digests and profile facts to a searchable index and an append-only store of originals. In practice, the brain is reached through several doorways. Claude, Codex, Cursor or any MCP client connects as a tool server, where a fast recall path lets an agent state its task in a line and receive the matching prompt or procedure the owner wrote, while grounded search returns facts, documents and tables with citations. Telegram, email, share links, team and client logins and an API cover the rest. A Toolsmith agent reads a service's API documentation and writes tested tools, with credentials kept in an encrypted vault, and heartbeats run scheduled routines. Ingestion covers email, Microsoft 365, Telegram, files, voice and subscribed calendars. Access control is a central design point. Four levels (admin, team, client and public) are enforced by the database, so answers match across the app and MCP. Content is treated as data rather than instructions to limit prompt injection. The whole stack runs on one Postgres instance covering vectors, graph, full-text search and queues, in a Docker-based deployment. Mantle suits developers, small teams, agencies with client portals and privacy-conscious organisations that want persistent context under their own control. Compared with hosted assistants or vector-database-based retrieval setups, it trades convenience for ownership and breadth. The stated ceiling is roughly 20,000 documents per brain, after which the recommended path is adding further brains that query each other through scoped federation grants.

How do you use Mantle?

  1. 1Check the install requirements
    Read the install page to see what the server needs before running anything. It explains the Docker-based setup and the model provider key.
    Mantle — Check the install requirements
  2. 2Install Mantle on your server
    Run the one-line install script on your own machine, or follow the server guide in the docs for a step-by-step setup.
    Mantle — Install Mantle on your server
  3. 3Add your first content
    Feed in files, mail or notes through Jackdaw or an ingestion pipeline. Facts, entities and embeddings are extracted automatically without tagging.
  4. 4Set up access levels
    Decide which items belong to Admin, Team, Client or Public, and invite members or clients so each reads only their tier.
    Mantle — Set up access levels
  5. 5Connect an MCP client
    Point Claude, Cursor or another MCP client at the brain so agents can recall your prompts and search your data with citations.
  6. 6Review the architecture
    Read the architecture page to understand memory layers, security borders and how federation between brains is enforced.
    Mantle — Review the architecture

Pros and cons

Pros

  • Works with existing AI clients through MCP rather than forcing a switch to a new assistantAI
  • Four database-enforced access levels cover admins, team members, clients and public share linksAI
  • Runs on a single Postgres with Docker services, keeping the stack lean and backups portableAI
  • Toolsmith agent builds and live-tests API tools from documentation, with secrets held in an encrypted vaultAI
  • Federation lets separate brains answer scoped queries with document-level grants and audit trailsAI

Cons

  • Self-hosting means the owner must run, secure and back up their own server and Docker servicesAI
  • The stated practical ceiling is about 20,000 documents per brain, so larger corpora need several brainsAI
  • A model provider is still required, so chat, embeddings and voice depend on an external key unless a local embedder is usedAI
  • Breadth of features (agents, federation, mini-apps, 284 MCP tools) suggests a steep learning curve for casual usersAI
  • Installation relies on a curl-piped shell script, which some security teams will want to audit firstAI

How much does Mantle cost?

Support

A documentation site covers installation and concepts such as access tiers, and the source code is published on GitHub. No support channels are described.

Integrations

Connects to Claude, Codex, Cursor and any MCP client. Ingests email, Microsoft 365 (SharePoint, OneDrive, Outlook), Telegram, files, voice and subscribed calendars. Toolsmith adds any service with API documentation.

Features

Layered memory with knowledge graph, grounded search with citations, MCP server with 284 tools, recall of prompts by task, Toolsmith API-tool builder, mini-apps, Agent Studio, heartbeats, Telegram, share links, team and client logins, and federation.

Learn more

Frequently asked questions about Mantle

  • Does Mantle have an API?
    Yes, Mantle offers an API.
  • How do you use Mantle?
    The walkthrough on this page covers 6 steps: 1. Check the install requirements 2. Install Mantle on your server 3. Add your first content 4. Set up access levels 5. Connect an MCP client 6. Review the architecture.
  • What platforms does Mantle support?
    Mantle is available on Web App.
  • What does Mantle integrate with?
    Connects to Claude, Codex, Cursor and any MCP client. Ingests email, Microsoft 365 (SharePoint, OneDrive, Outlook), Telegram, files, voice and subscribed calendars. Toolsmith adds any service with API documentation.
  • What are the limitations of Mantle?
    Self-hosting means the owner must run, secure and back up their own server and Docker services. The stated practical ceiling is about 20,000 documents per brain, so larger corpora need several brains. A model provider is still required, so chat, embeddings and voice depend on an external key unless a local embedder is used.

Status

StatusActive
Views0
Outbound clicks0
Added10/8/2026

Platforms

Web App

Pricing

Free