"Using Claude in Cursor to Run and Read Outputs from PowerShell or Terminal" matching MCP servers:

An agent-capable MCP server with terminal access, filesystem control, and persistent memory. It includes sandboxing, access control, activity logging, and a file-backed memory store for context across conversations.

Persistent memory and pattern learning for AI coding assistants via MCP.

Scoped, low-latency persistent memory layer for AI agents, Cursor, and Claude Code over Model Context Protocol with sub-50ms hybrid search.

A local MCP server that lets LLM agents read EPUB books and PDF documents with outline-first navigation, precise node reads, and local SQLite persistence.

Provides structured external memory for AI assistants, enabling persistent context, branch notes, tacit knowledge, and checklists to overcome AI memory loss and context confusion.

Read-only bridge between Claude Code and Cursor on Windows. Exposes Cursor's local chat database via 7 MCP tools, plus a 5-min background poller. The server starts and responds to introspection in a container, but tool calls require a Windows host with Cursor installed (the container is for directory checks only).

Enables read-only access to a local Zotero Desktop library, providing search, recent items, metadata, tags, collections, PDF attachments, and full-text search through a browser UI or MCP endpoint.

A persistent SQLite-backed storage server that enables Cursor IDE's AI assistant to remember information across sessions with global or project-specific scopes. It supports complete CRUD operations, tag-based organization, and keyword search to manage user preferences and context effectively.

Pull Deep Memory from across your Claude Code Sessions — when you need it.

An MCP server that reads all your Claude Code project memory files and exposes them as tools. Lets any Claude instance — in any project, or via Claude.ai — query your full project history and preferences.

Provides Claude Code with cross-session long-term memory via Letta, allowing it to read and store project context, learnings, and decisions.

A persistent semantic memory system for Claude Code that provides a structured, versioned document store with semantic search and graph visualization. It acts as a memoization layer to store and retrieve research, design decisions, and codebase insights across different work sessions.

Self-improving learning engine for Claude Code. Extracts signals from sessions (corrections, successes,confusion), runs periodic reflections, and evolves behavioral frameworks through evidence. 9 MCP tools, automatichooks, local-only.

An MCP server that gives Claude persistent, locally-stored memory with verification-gated lessons and a Pattern Oracle to prevent unverified guesses from becoming ingrained facts.

Post-hoc session handoff and project memory for Claude Code: MCP tools list_sessions and handoff turn any session — even crashed or usage-limit-hit ones — into a clean handoff.md another model can continue from, with secrets redacted from every output. Zero dependencies, fully local; also distills a project's entire session history into one cited memory brief.

Enables Claude Code to maintain a persistent todo list stored in SQLite, with tools to list, search, add, update, complete, and delete todos across sessions.

MCP server that lets you search your Claude Code conversation history to find past solutions, track file changes, and learn from previous work.

An MCP server that enables Claude to learn from user corrections by recording them as persistent rules in CLAUDE.md files. It manages project-specific or global guidelines to ensure the assistant avoids repeating the same mistakes in future sessions.

Provides sophisticated context management for Claude, enabling persistent context across sessions, project-specific organization, and conversation continuity.

Persistent memory and session intelligence for AI coding assistants. Auto-tracks mistakes, decisions, and context via hooks. Mines your full session history for patterns, predictions, and cross-session search.