Zeus Memory — Enterprise Intelligence Platform MCP server

Add the server

claude mcp add --transport http zeus-memory https://zeus.aldc.io/mcp --header 'X-API-Key: <X-API-KEY>'

Fill in your credentials

Replace <X-API-KEY> with your real value. Keep secrets out of any config file you commit.

Verify it's connected

claude mcp list

Sharing it with your team?

Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

Use it in a session

Ask Claude to use the tools this server exposes. It discovers them automatically.

Open your MCP config

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

Add this server

{
  "mcpServers": {
    "zeus-memory": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://zeus.aldc.io/mcp",
        "--header",
        "X-API-Key:${X_API_KEY}"
      ],
      "env": {
        "X_API_KEY": "<X-API-KEY>"
      }
    }
  }
}

Fill in your credentials

Replace <X-API-KEY> with your real value. Keep secrets out of any config file you commit.

Why the wrapper?

This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.

Restart Claude Desktop

The tools appear under the 🔌 menu once the app reloads.

Create / edit .cursor/mcp.json in your project

{
  "mcpServers": {
    "zeus-memory": {
      "url": "https://zeus.aldc.io/mcp",
      "headers": {
        "X-API-Key": "<X-API-KEY>"
      }
    }
  }
}

Fill in your credentials

Replace <X-API-KEY> with your real value. Keep secrets out of any config file you commit.

Enable it

Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

Add to ~/.codex/config.toml

[mcp_servers.zeus-memory]
command = "npx"
args = ["-y", "mcp-remote", "https://zeus.aldc.io/mcp", "--header", "X-API-Key:${X_API_KEY}"]
env = { X_API_KEY = "<X-API-KEY>" }

Fill in your credentials

Replace <X-API-KEY> with your real value. Keep secrets out of any config file you commit.

Why the wrapper?

Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.

Run Codex

Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

Edit ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "zeus-memory": {
      "serverUrl": "https://zeus.aldc.io/mcp",
      "headers": {
        "X-API-Key": "<X-API-KEY>"
      }
    }
  }
}

Fill in your credentials

Replace <X-API-KEY> with your real value. Keep secrets out of any config file you commit.

Reload

Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

Open Cline → MCP Servers → Configure

Adds to cline_mcp_settings.json.

Add the server

{
  "mcpServers": {
    "zeus-memory": {
      "type": "streamableHttp",
      "url": "https://zeus.aldc.io/mcp",
      "headers": {
        "X-API-Key": "<X-API-KEY>"
      }
    }
  }
}

Fill in your credentials

Replace <X-API-KEY> with your real value. Keep secrets out of any config file you commit.

Create .vscode/mcp.json

{
  "servers": {
    "zeus-memory": {
      "type": "http",
      "url": "https://zeus.aldc.io/mcp",
      "headers": {
        "X-API-Key": "<X-API-KEY>"
      }
    }
  }
}

Fill in your credentials

Replace <X-API-KEY> with your real value. Keep secrets out of any config file you commit.

Start it

VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.