IDE Memory MCP

    1

    Persistent, cross-IDE project memory for AI agents via MCP.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    IDE Memory MCP

    Example session with this skill installed

    Initialize memory for this project and tell me what we were working on last.

    • Read your context and instructions
    • Compiled the ide memory mcp

    I have initialized the project memory and retrieved the active context. It looks like you were in the middle of refactoring the authentication middleware.

    Project Memory Summary

    SectionSizeLast UpdatedStatus
    overview1.2kb2 days agoCurrent
    decisions0.8kb5 days agoCurrent
    active_context2.4kb1 hour agoActive
    progress1.5kb1 hour agoActive

    Current Work State (active_context)

    The primary focus is replacing the legacy JWT verification in /src/middleware/auth.ts with the new @auth/core implementation.

    • Completed: Installed dependencies, drafted new schema.
    • In Progress: Updating validateSession to handle the new token format.
    • Blockers: Waiting for confirmation on the redirect URL for the OAuth callback.

    Recent Decisions

    • 2023-10-24: Switched to @auth/core to simplify multi-provider support.
    • 2023-10-20: Chose Redis for session caching to handle horizontal scaling.

    Next steps

    1. Finish the validateSession logic in auth.ts.
    2. Run the existing test suite to check for regressions in the login flow.
    3. Update the progress section once the middleware tests pass.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Stop losing context every time you start a new chat or switch IDEs. This skill interfaces with the ide-memory MCP server to store architectural decisions, project progress, and active work states in local Markdown files, ensuring your agent remembers the project across Claude Code, Cursor, VS Code, and Windsurf.

    What it does

    • Persistent Context maintains a project-specific memory that survives chat resets and IDE restarts.
    • Cross-IDE Sync shares the same memory files across any MCP-compatible environment including Cursor and Claude Desktop.
    • Automated Bootstrapping scans READMEs and config files to initialize memory for new projects.
    • Selective Retrieval loads only relevant sections like decisions or active_context to save tokens.
    • Historical Snapshots recovers previous versions of memory sections using built-in versioning.

    How it works

    1. Initialize the project by calling init_project at the start of a session to detect the root path and git remote.
    2. Review the summary table to identify stale sections or high-level project status without loading full content.
    3. Read specific sections or query the memory for keywords to pull relevant context into the current chat.
    4. Update memory after significant changes or decisions to ensure the next session starts with an accurate state.

    Frameworks & tools

    Requires the ide-memory MCP server installed locally. Works with any stack including Node.js, Python, Rust, and Go by parsing standard project manifests.

    Why this beats prompting it yourself

    Manual context setting is repetitive and error-prone. This skill automates the retrieval and storage of technical debt, rationale, and progress, preventing "hallucinated" project states that often occur in long-running development threads.

    Use cases

    • Resuming Work after a break by reloading the exact active_context and TODO list from the previous day.
    • Onboarding Agents to a new codebase by having the tool scan and summarize the architecture into memory.
    • Tracking Decisions to ensure the agent remembers why a specific library or pattern was chosen months ago.
    • Cross-Tool Handoff moving from a terminal-based agent to a GUI IDE while keeping the current task state intact.

    Known limitations

    Requires local installation of the ide-memory MCP server. Does not store secrets or credentials. Performance may degrade if individual memory sections exceed 10k characters without pruning.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Requires ide-memory MCP server. No support for storing secrets or .env values. Manual pruning required for sections exceeding 10k characters.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 16 days ago

    • Free with an Agensi account

    Software
    IDE Memory MCPPython

    Permissions

    Read Files
    Network Access
    Listed16 days ago

    What's inside

    Frequently Asked Questions

    This skill solves 'context loss' by providing a persistent, local Markdown-based memory. Instead of re-explaining your project goals and architectural choices in every new chat, the agent can instantly recall previous decisions and the current 'active_context'.

    The skill is compatible with any MCP-enabled environment, including Claude Code, Cursor, VS Code, and Windsurf. Because it uses local files, your project memory remains consistent even if you switch between a terminal-based agent and a GUI-based IDE.

    To use this skill, you must have the `ide-memory` MCP server installed on your local machine. Once installed, the skill uses standard project manifests (like package.json or requirements.txt) to automatically map and manage memory for your specific workspace.

    No, all memory is stored in local Markdown files within your project environment. This ensures your project data remains private and allows you to manually inspect or edit the memory files if needed.

    The skill includes a built-in snapshot system that allows you to recover previous versions of memory sections. This is particularly useful for auditing past architectural decisions or reverting memory if an agent inadvertently overwrites a section with incorrect information.

    While the skill handles large projects efficiently by loading only relevant sections (like 'decisions' or 'active_context'), it is recommended to keep individual memory sections under 10,000 characters to optimize token usage and response speed.

    New in LLM Ops

    Free