Vertiso Memory for JetBrains IDEs

One memory, every agent

Decide it anywhere. JetBrains IDEs already knows.

What you settle in one tool is on hand in JetBrains IDEs, typed and waiting for your confirmation.

Claude Desktop 9:41 AM

You Heads up: the billing cutover moves to Oct 14. Stripe webhooks stay on v2 until then.

Claude Noted. I saved that as a decision with the v2 constraint attached, dated today.

Remembered · decision · constraint

Same room

JetBrains · new session 9:42 AM

You Start the webhook migration branch.

AI Assistant Your memory says the cutover is Oct 14 and v2 stays live until then. I'll scaffold the v3 handler behind a flag and leave v2 untouched.

Recalled · decision · nothing re-explained

times you repeat yourself

8 types

decision, constraint, action, and more

You confirm

nothing closes itself

Install in JetBrains IDEs

The same steps as the install guide, for this tool only: a live Marketplace listing where one exists, the public plugin repository, native HTTP MCP, then the local vmem bridge.

Vertiso Memory MCP URL

https://memory.vertiso.ai/mcp

Until the JetBrains Marketplace listing is public, build the plugin from Vertiso's public GitHub repository and install the generated ZIP from Settings → Plugins → Install Plugin from Disk. After publication, uninstall the local 1.0.0 build before installing from the Marketplace so it owns future updates.

JetBrains plugin source (GitHub)

# Build-only requirement: Java 21
git clone https://github.com/Vertiso/memory-jetbrains.git
cd memory-jetbrains
./gradlew verifyPluginArchive
# Install build/distributions/*.zip with "Install Plugin from Disk..."

JetBrains uses Vertiso Memory's local STDIO bridge, so the vmem CLI is required and must be initialized before configuration.

After installation, choose Tools → Configure Vertiso Memory MCP, copy the generated configuration into Settings → Tools → AI Assistant → Model Context Protocol (MCP), then choose Tools → Install Vertiso Memory Skills if you want the four bundled skills.

JetBrains MCP config (vmem bridge)

{
  "mcpServers": {
    "vertiso-memory": {
      "command": "<run `which vmem` to get the absolute path>",
      "args": ["mcp", "serve", "--client", "jetbrains"]
    }
  }
}

For Junie, Claude, and Codex, also enable Settings → Tools → AI Assistant → Agents → Pass custom MCP servers.

Connected? Start a new conversation and say Hello. Your assistant greets you by name and mentions what it remembers. The standing instruction and the first conversation →

API token

Only the vmem bridge and the bearer-token fallbacks need one. OAuth clients sign in during the handshake instead.

Power users: the vmem CLI

A native binary for working memory from the terminal, and a stdio-to-HTTP bridge for clients that cannot reach a remote server. It keeps your token in ~/.vmem instead of each app's config.

Install vmem

curl -fsSL https://memory.vertiso.ai/install.sh | sh

Every vmem command →

Your memory, inside JetBrains IDEs.

Decide it anywhere. JetBrains IDEs already knows.

Install in JetBrains IDEs

Start building your memory layer.