Cursor + Ambience.
Updated 2026-06-07 · Shared agent memory
A governed team memory layer for Cursor and other MCP-speaking developer agents.
Ambience gives Cursor access to scoped shared context through MCP, so project decisions and team conventions can follow the work rather than stay trapped in one user's local memory.
MCP-native memory
Cursor can connect to the Ambience MCP server to search, read, and save memories. Ambience handles scope checks and redaction at the memory layer.
Project context that survives
When a Cursor session uncovers a durable project decision or failure mode, saving it to Ambience makes it available to future approved agents, including Claude Code and Codex.
The advantage over local-only memory
Local memory helps one developer. Ambience helps the team: shared scopes, source links, admin controls, conflict review, and audit history.