Vertiso Memory
OfficialProvides cross-agent memory recall and search, explicit memory creation with safety controls, and Agent Skills for checkpoints, handoffs, handoff resume, and wrap-up, enabling GitHub Copilot and other MCP-capable agents to use portable, user-owned memory.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Vertiso MemoryRemember that my favorite color is blue"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Vertiso Memory for VS Code
Vertiso Memory gives GitHub Copilot and other MCP-capable agents in VS Code a portable, user-owned memory that follows you between tools.
The extension registers Vertiso Memory's remote MCP server and four Agent Skills with VS Code. VS Code performs the OAuth sign-in and stores the resulting authorization. The extension does not read or retain your Vertiso credentials.
Install from the public source repository
Until the Marketplace listing is live, build the extension from its public source repository:
Build-only requirements: Node.js 24 and npm.
git clone https://github.com/Vertiso/memory-vscode.git
cd memory-vscode
npm ci
npm run packageIn VS Code, run Extensions: Install from VSIX... and select
build/vertiso-memory-vscode.vsix. A locally installed VSIX does not provide
the Marketplace's normal update path. After publication, uninstall this local
1.0.0 build and install the Marketplace version so the Marketplace owns future
updates.
Related MCP server: mcp-chest-memory
Connect
Install the extension.
Open Chat in VS Code and view the available MCP servers.
Start Vertiso Memory and complete the browser sign-in when VS Code asks.
Ask the agent to remember or recall something.
Existing manual Vertiso Memory entries in mcp.json should be removed to avoid
showing the same server twice.
What it provides
Cross-agent memory recall and search.
Explicit memory creation with safety controls.
Agent Skills for checkpoints, handoffs, handoff resume, and wrap-up.
OAuth authentication managed by VS Code.
Optional SessionStart primer
The extension does not silently write files under ~/.copilot or install a
SessionStart hook. The MCP server instructions provide the normal session
primer.
To opt into CLI-managed VS Code setup, including user-directory skill copies
and a vmem hello SessionStart hook, run:
vmem mcp install vscodeUse either the extension's remote OAuth MCP setup or the CLI-managed setup. Using both can show Vertiso Memory twice in the MCP server list.
Vertiso Memory only stores information when you or your agent explicitly calls its tools. It refuses secrets and other inappropriate memory content. See the privacy policy and documentation for details.
Support
Visit Vertiso Memory support to report a
problem or ask a question. Source and issue tracking live in the public
Vertiso/memory-vscode
repository.
This repository is a generated public mirror of Vertiso Memory's canonical distribution source. Open issues here, but do not submit pull requests or emergency source changes directly: the next mirror run replaces the repository tree. Contact support when a source change is required.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vertiso/memory-vscode'
If you have feedback or need assistance with the MCP directory API, please join our Discord server