Skip to main content
Memory builds a private, searchable knowledge base out of the tools you’ve connected. Instead of your AI agent calling one tool at a time, it can ask Memory a question and get an answer synthesized across all your data at once — “who followed up with Acme last week?”, “what did the team say about the launch?”, “how many people had a work anniversary this month?”. Everything lives under Settings → Memory in your dashboard.

​
What the Memory page shows

The page has two parts:
  • Memory (the master switch) — the on/off toggle for the whole feature, plus your current storage used and cost this period.
  • Indexed Connections — every connected data source, each with its own toggle and a live status badge (for example Ready · 128 indexed).

​
What “indexing” means

When a connection is included, RouteMCP reads its records (emails, messages, calendar events, files, CRM records), pulls out the people, organizations, and facts in them, and stores those in the knowledge base. That process is indexing. The badge on each connection tells you where it is:
  • Starting indexing… — RouteMCP has just begun and is fetching the first records.
  • Indexing… — records are actively being processed. Large accounts take a while; this runs in the background, so you can leave the page.
  • Ready · N indexed — done. N is how many records are searchable, and your agent can now use them.
You don’t have to wait on the page — indexing continues on its own, and new records are picked up over time.

​
Turning Memory on and off

  • The master switch turns the whole feature on or off. While it’s off, nothing is indexed and your agent can’t search Memory.
  • Each connection’s toggle decides whether that source is included in the index.
Turning a connection off doesn’t delete what was already indexed — it just stops adding new records from that source and removes it from your agent’s search. Turn it back on to resume.

​
Cost

Indexing uses AI to read and understand your records, so it has a cost, shown as cost this period on the page. The initial index of a busy account is the largest one-time cost; after that, only new records are processed, which is much cheaper.

​
Supported connections

Memory currently supports a subset of RouteMCP’s integrations — see the list in the July 2026 changelog. Connections outside that list can still be used through the router and playground, but won’t appear in the Memory index yet. More are being added.