vx-plugins

@vesselnyc/mcp-server

Plugin-first VX memory for Claude, Codex, Cursor, OpenClaw, and other MCP clients.

VX gives your assistant durable memory for:

• user preferences
• project decisions
• setup choices
• recurring workflows
• imported notes or prior chat history

Users get more continuity across sessions and spend less time repeating themselves.

Requirements

• Node.js 18 or newer
• A VX API base URL, usually https://api.vx.dev/v1
• One VX credential: VX_API_KEY or VX_BEARER_TOKEN

Quick Start

Claude Code

Default path:

npx @vesselnyc/mcp-server install claude

This installs:

• the packaged VX MCP server in Claude Code
• a bundled /vx-memory slash command with the recommended recall/store/import workflow

Secondary path: Claude Code plugin marketplace

/plugin marketplace add vx-nyc/vx-mcp
/plugin install vx-mcp

Fallback: Claude Desktop MCP config

{
  "mcpServers": {
    "vx": {
      "command": "npx",
      "args": ["-y", "@vesselnyc/mcp-server@latest", "mcp"],
      "env": {
        "VX_API_BASE_URL": "https://api.vx.dev/v1",
        "VX_API_KEY": "your-api-key",
        "VX_NAME": "VX",
        "VX_SOURCE": "claude-desktop"
      }
    }
  }
}

Codex

Default path:

npx @vesselnyc/mcp-server install codex

This installs:

• the packaged VX MCP server in ~/.codex/config.toml
• a bundled Codex skill at ~/.codex/skills/vx-memory/SKILL.md

Direct CLI fallback:

codex mcp add vx -- npx -y @vesselnyc/mcp-server@latest mcp

Manual ~/.codex/config.toml fallback:

[mcp_servers.vx]
command = "npx"
args = ["-y", "@vesselnyc/mcp-server@latest", "mcp"]

[mcp_servers.vx.env]
VX_API_BASE_URL = "https://api.vx.dev/v1"
VX_API_KEY = "your-api-key"
VX_NAME = "VX"
VX_SOURCE = "codex"

Cursor

One-click install:

After adding it, set your VX credential in Cursor before first use.

Manual .cursor/mcp.json fallback:

{
  "mcpServers": {
    "vx": {
      "command": "npx",
      "args": ["-y", "@vesselnyc/mcp-server@latest", "mcp"],
      "env": {
        "VX_API_BASE_URL": "https://api.vx.dev/v1",
        "VX_API_KEY": "your-api-key",
        "VX_NAME": "VX",
        "VX_SOURCE": "cursor"
      }
    }
  }
}

OpenClaw

Install the native plugin:

openclaw plugins install @vesselnyc/mcp-server
openclaw gateway restart

Add plugin config once:

{
  plugins: {
    entries: {
      "vx-memory": {
        enabled: true,
        config: {
          apiBaseUrl: "https://api.vx.dev/v1",
          apiKey: "your-api-key",
          source: "openclaw",
          name: "VX",
          storeOnRequestOnly: false,
          maxTokens: 4000
        }
      }
    }
  }
}

Verify setup:

1. Ask OpenClaw to run vx_status.
2. Store one small preference with vx_store.
3. Recall it with vx_recall or vx_context.

Compared with regular OpenClaw, VX adds durable recall of preferences, decisions, imported history, and recurring workflows across sessions.

NemoClaw

If your NemoClaw deployment supports OpenClaw plugins, use the same install and config flow as OpenClaw.

If it exposes MCP configuration instead, use the standard MCP config shown below with VX_SOURCE set to openclaw or nemoclaw.

Standard MCP Config

Use this in any MCP client that accepts a local command:

{
  "mcpServers": {
    "vx": {
      "command": "npx",
      "args": ["-y", "@vesselnyc/mcp-server@latest", "mcp"],
      "env": {
        "VX_API_BASE_URL": "https://api.vx.dev/v1",
        "VX_API_KEY": "your-api-key",
        "VX_NAME": "VX",
        "VX_SOURCE": "mcp"
      }
    }
  }
}

Bundled Guidance

This package ships host-specific guidance so the memory workflow feels native instead of generic:

• Claude Code: bundled /vx-memory slash command
• Codex: bundled vx-memory skill
• OpenClaw: bundled vx-memory skill plus native vx_status
• MCP prompts: vx_memory_workflow and vx_memory_import

Recommended workflow in every host: