"Cursor Not Losing Memory or State" matching MCP servers:

Persistent, branch-aware workflow state memory MCP server for AI coding assistants. Tracks tasks, accepted decisions, and active blockers to prevent session context bloat and speed up development.

Renders a YAML CV into a one-page PDF via notboringresume.cloud, optionally generating a cover letter adapted to the resume and job offer.

An MCP-native state sidecar that externalises workflow state for distributed agent deployments.

Provides state and log management tools designed for long-lived AI agents that may be interrupted and resumed. It enables tracking agent progress and maintaining an append-only event history to ensure continuity across multiple sessions.

A FastMCP server for Cursor platform APIs enabling spend guardrails, cloud agent monitoring, and inter-agent inbox messaging.

An MCP server that lets Claude spawn Cursor subagents as async, bounded workers, enabling non-blocking task delegation with asynchronous completion notifications.

Enables interactive feedback with image support in Cursor, allowing users to paste images for visual context and feedback.

Persistent project memory for AI models and coding agents. Memory MCP stores architecture, decisions, tasks, warnings, preferences, and session state in Supabase so OpenCode, Claude Code CLI, Qwen Code, Codex, or any MCP-compatible client can resume work without losing context.

Hosted memory for AI agents that learns from outcomes, with shared rooms. One key across Claude, Cursor & ChatGPT.

Enables progress-triggered text-to-speech in Cursor Agent, with speak and stop controls and voice matching the system UI language.

Enables AI assistants and other MCP clients to launch and steer Cursor Cloud Agents on repositories or as repo-less research tasks, including model selection, mid-run follow-ups, cancellation, result retrieval, and run listing. Also exposes authentication checks and per-agent or per-run token usage and cost reporting.

Enables AI assistants and MCP clients to launch and manage Cursor Cloud Agents on repositories or without one, select models, follow up mid-run, retrieve or cancel results, and check usage and cost.

A different approach from typical persistent-memory MCPs. Instead of a local SQLite + embeddings store, the memory lives as plain files in a .ai-memory/ directory you commit to your repo (facts.jsonl, decisions/\*.md, gotchas.md). Git is the sync layer — what one Claude/Cursor/Cline learns about a repo, the next session (or a teammate's agent) picks up automatically. 5 MCP tools: get_rep

MARM MCP provides persistent memory and structured session context beneath any AI tool, so your agents learn, remember, and collaborate across all your workflows.

Enables AI agents to maintain long-term, cross-session memory by extracting facts, reconciling state conflicts, and retrieving relevant memories via vector search.

Provides persistent memory for Claude with hierarchical categorization, cross-corpus recall, session journals, and customizable persona, enabling memory continuity across sessions.

Enables Claude Desktop and compatible agents to search, read, add, update, and delete a locally stored, user-curated memory using hybrid retrieval with reranking and Qdrant. All processing runs locally without cloud services or API keys.

Two-layer memory for AI agents. Episodes compress into identity. The only MCP memory server with an immune system. Patterns earn permanence through evidence, false knowledge gets caught and demoted, and stale information fades — so your agent's memory gets smarter over time, not just bigger. Zero dependencies. 5 tools. Works with any MCP client.

An MCP server that lets users capture quick phone thoughts via Android and later query them from AI assistants like Grok or Claude, functioning as a simple task memory store without notifications or geolocation.

MCP server exposing Cursor's HTTP APIs for managing Cloud Agents, Team/Org Admin, Analytics, Bugbot, AI Code Tracking, and Fleet with read-only and read-write modes.