Skip to main content

Integrations

The Memsolus MCP server runs over stdio (default) or HTTP. Any client that supports the Model Context Protocol can use it.

Claude Desktop​

Config file location

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Configuration

{
  "mcpServers": {
    "memsolus": {
      "command": "npx",
      "args": ["-y", "@memsolus/mcp"],
      "env": {
        "MEMSOLUS_API_KEY": "msk_live_your_key_here",
        "MEMSOLUS_WORKSPACE_ID": "your-workspace-uuid"
      }
    }
  }
}

After saving, restart Claude Desktop completely. The Memsolus tools will appear in the tools panel.

Using Bun instead of Node

{
  "mcpServers": {
    "memsolus": {
      "command": "bunx",
      "args": ["@memsolus/mcp"],
      "env": {
        "MEMSOLUS_API_KEY": "msk_live_your_key_here",
        "MEMSOLUS_WORKSPACE_ID": "your-workspace-uuid"
      }
    }
  }
}

Claude Code​

Claude Code supports MCP servers at both the project and user level.

Project-level (shared with the team)

Add to .claude/settings.json in your project root:

{
  "mcpServers": {
    "memsolus": {
      "command": "npx",
      "args": ["-y", "@memsolus/mcp"],
      "env": {
        "MEMSOLUS_API_KEY": "msk_live_your_key_here",
        "MEMSOLUS_WORKSPACE_ID": "your-workspace-uuid"
      }
    }
  }
}

Via Claude CLI

claude mcp add memsolus \
  -e MEMSOLUS_API_KEY=msk_live_your_key_here \
  -e MEMSOLUS_WORKSPACE_ID=your-workspace-uuid \
  -- npx -y @memsolus/mcp

Verify the server is registered:

claude mcp list

Cursor​

Cursor uses the same JSON format as Claude Desktop. Open Settings > MCP and add the server configuration, or create a .cursor/mcp.json file in your project:

{
  "mcpServers": {
    "memsolus": {
      "command": "npx",
      "args": ["-y", "@memsolus/mcp"],
      "env": {
        "MEMSOLUS_API_KEY": "msk_live_your_key_here",
        "MEMSOLUS_WORKSPACE_ID": "your-workspace-uuid"
      }
    }
  }
}

Restart Cursor after saving the configuration.

Other MCP clients​

Any MCP client that supports the stdio transport can connect to the Memsolus MCP server. The server reads from stdin and writes to stdout following the MCP protocol.

Generic stdio configuration

{
  "mcpServers": {
    "memsolus": {
      "command": "npx",
      "args": ["-y", "@memsolus/mcp"],
      "env": {
        "MEMSOLUS_API_KEY": "msk_live_your_key_here"
      }
    }
  }
}

Consult your client's documentation for the exact file path and format.

HTTP mode​

Run the MCP server as an HTTP server for clients that do not support stdio, or for multi-agent setups where multiple clients connect to the same server instance.

Start in HTTP mode

MEMSOLUS_API_KEY=msk_live_... npx @memsolus/mcp --http --port 3001

The server listens on http://localhost:3001 and accepts connections via the SSE transport.

Docker

FROM node:20-alpine
RUN npm install -g @memsolus/mcp
EXPOSE 3001
CMD ["memsolus-mcp", "--http", "--port", "3001"]
services:
  memsolus-mcp:
    build: .
    environment:
      MEMSOLUS_API_KEY: ${MEMSOLUS_API_KEY}
      MEMSOLUS_WORKSPACE_ID: ${MEMSOLUS_WORKSPACE_ID}
    ports:
      - "3001:3001"

Troubleshooting​

"API key not provided"​

MEMSOLUS_API_KEY must be set in the env block inside the memsolus entry — not at the top level of the JSON file.

Check your config matches this structure:

{
  "mcpServers": {
    "memsolus": {          ← correct level
      "env": {
        "MEMSOLUS_API_KEY": "msk_live_..."
      }
    }
  }
}

"Workspace not found"​

The MEMSOLUS_WORKSPACE_ID you provided does not exist or the API key does not have access to it. Verify the workspace UUID in the Memsolus dashboard.

If MEMSOLUS_WORKSPACE_ID is not set, the server uses the default workspace associated with your API key.

"Unauthorized" or invalid API key​

The API key may be expired, revoked, or copied incorrectly. Generate a new key in the Memsolus dashboard and update your configuration.

Tools not appearing in Claude​

  1. Confirm the configuration file was saved correctly — validate the JSON syntax before restarting.
  2. Restart Claude Desktop completely (quit the app, not just the window).
  3. Ask Claude: "What MCP tools do you have access to?" — if Memsolus tools are missing, check the Claude Desktop logs for MCP connection errors.
  4. If you see a spawn error, verify that npx or bunx is in your system PATH.

Timeout errors​

The MCP server forwards requests to the Memsolus API. If requests time out:

  • Confirm the API key is valid and the API is reachable from your machine
  • For the HTTP mode setup, verify the port is not blocked by a local firewall

Permission errors on specific tools​

The API key may be missing required scopes. Permissions needed per tool category:

CategoryRequired scope
Memory read operationsmemory.read
Memory write operationsmemory.write
Memory deletememory.delete
Knowledgeknowledge.read
Graphknowledge.read
Dashboardmemory.read

See Authentication to check and update your key's permissions.