Configure Memory MCP + SDK

Your agent remembers. Users shouldn't have to repeat themselves.

Today we're releasing Configure Memory β€” persistent, cross-agent memory for AI applications.

Every AI conversation starts from scratch. Your agent doesn't know the user prefers window seats. Doesn't know they're vegetarian. Doesn't remember they mentioned a trip to Tokyo last week.

Users repeat themselves constantly. Context is lost between sessions, between agents, between platforms. The AI feels stateless because it is.

We think agents should remember.

The idea

Configure Memory gives your agent a persistent understanding of each user. Not just chat history β€” real context. Their preferences, their connected apps, their world.

When a user talks to your agent, Memory surfaces what matters. Automatically. The user mentions travel? Memory knows they prefer Delta, usually book window seats, and have a trip to Barcelona coming up.

Your agent doesn't have to ask. It just knows.

How users experience it

Users authenticate once with their phone. Simple, secure, no passwords.

πŸ‡ΊπŸ‡Έ
+1 (888) 888-8888 Phone

By continuing, you agree to Memory's Terms of Service

They verify with a code. Auto-fills from SMS. Takes seconds.

4
7
2
_
_
_

we sent a code to +1 (415) 555-0123

resend in 28s

Then they connect their tools. Gmail, Calendar, whatever they use. One tap each.

βœ‰
Gmail βœ“ connected
πŸ“…
Google Calendar connect
πŸ“
Notion connect

From then on, every agent they talk to gets context. Their memories persist, grow, compound over time.

β—‰ Saved Memories βš™
prefers window seats on flights
vegetarian, no shellfish
lives in SF, works in tech
planning trip to Tokyo in April
see more

A travel agent sees flight bookings and hotel preferences. A fitness agent sees workout schedules. Each agent gets what's relevant β€” nothing more.

Users control everything. They can see exactly what each agent knows, revoke access anytime, delete their data completely. It's their memory.

For developers

Two ways to integrate. Both take minutes.

MCP: One line in your config

If you're building with Claude or any MCP-compatible client, just add our server to your config:

{
  "mcpServers": {
    "memory": {
      "url": "https://api.configure.dev/mcp",
      "headers": { "X-App-Key": "your-key" }
    }
  }
}

That's it. Your agent sees the Memory tools. Context flows automatically.

SDK: Drop-in components

Want the full UI? Our SDK gives you the components you saw above β€” phone auth, OTP, connections, memory cards. Ship a complete memory experience in your app.

import { PhoneInput, OTPInput, MemoryCard } from '@configure/sdk';

// Your users authenticate, connect tools, see their memories
// All handled. All styled. All yours.

You don't build memory infrastructure. You don't manage user data stores. You don't write context retrieval logic. You just connect to Memory, and context flows.

Memory is smart about what it surfaces. It learns what your agent cares about and filters accordingly. A travel agent doesn't need to see grocery lists. A coding assistant doesn't need calendar events.

You focus on what your agent does. We handle what it knows.

What this means

Today, every agent is an island. Users rebuild context from scratch with each new tool they try. Preferences are forgotten. History is lost. The AI never gets smarter.

We're building something different.

A world where users build a profile over time. Where every conversation adds to what agents know. Where switching to a new app doesn't mean starting over.

Memory that compounds. Context that travels. Agents that actually understand.

For developers: you get rich user context without building infrastructure. For users: AI that finally feels personal.

Configure Memory is available to select design partners.