Skip to content

On this page you will connect MMW to VS Code over direct HTTP without storing your key in plain text in the repository, and verify the connection.

  • The remember, search, forget, validate_memory and gateway_call tools in VS Code chat in agent mode.
  • Memory shared with Claude Code, Cursor, Codex and claude.ai when the key belongs to the same account and project.
  • Nothing to install: the connection goes straight over HTTPS.
  • An MMW API key (starts with mmw_); see the Quickstart.
  • VS Code with MCP server support and chat in agent mode.
  1. Create .vscode/mcp.json in the project root. To use MMW in every project, use your user-level MCP configuration instead (the “MCP: Open User Configuration” command in versions that have it).

  2. Add the server. Rather than writing the key into the file, have VS Code prompt for it:

    .vscode/mcp.json
    {
    "inputs": [
    {
    "type": "promptString",
    "id": "mmw-key",
    "description": "MMW API key",
    "password": true
    }
    ],
    "servers": {
    "mmw": {
    "type": "http",
    "url": "https://mcp.mmwhub.tech/mcp",
    "headers": { "Authorization": "Bearer ${input:mmw-key}" }
    }
    }
    }

    VS Code asks for the key the first time the server starts and keeps it in its secure storage.

  3. Start the server: a Start link appears above the mmw block in the editor, or run “MCP: List Servers” and start mmw from there.

  1. Open VS Code chat and switch it to agent mode.

  2. Click the tools picker: the list should include the mmw server with remember, search, forget, validate_memory and gateway_call.

  3. Ask:

    Remember in MMW: staging is deployed with the systemd unit app-staging. Fact key: deploy-staging.

    VS Code may ask you to confirm the remember call; once confirmed, the record is saved with the unverified status.

  4. In a new chat ask:

    How do we deploy staging? Check MMW.

    Expected answer: the agent calls search and replies that staging is deployed with app-staging.