564 MCP Setup B197b065

MCP Server Configuration Guide

This guide explains how to properly configure aleph as an MCP server in all major MCP-compatible clients: Cursor, VS Code, Claude Desktop, OpenAI Codex, Windsurf, and others. It focuses on aleph, which supports action tools and workspace scoping.

Quick Start (Full Power Mode)

For maximum capability without needing to configure workspace roots:

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": ["--enable-actions", "--workspace-mode", "any", "--tool-docs", "concise"]
    }
  }
}

This enables:

• All action tools (read_file, write_file, run_command, run_tests)
• Any git repo access (not limited to a single workspace root)
• Concise tool descriptions (cleaner MCP tool list)

Shared Sub-Query Sessions (Live Sandbox)

If you want CLI sub-agents spawned via sub_query to access the same live Aleph session (tools, contexts, and sandbox state), enable streamable HTTP sharing:

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": ["--enable-actions", "--workspace-mode", "any", "--tool-docs", "concise"],
      "env": {
        "ALEPH_SUB_QUERY_SHARE_SESSION": "true",
        "ALEPH_SUB_QUERY_HTTP_PORT": "8765",
        "ALEPH_SUB_QUERY_MCP_SERVER_NAME": "aleph_shared"
      }
    }
  }
}

Notes:

• The Aleph server will spin up a local streamable HTTP endpoint on demand.
• CLI sub-agents (claude/codex/gemini) will be pointed at that live server automatically.
• Customize host/path with ALEPH_SUB_QUERY_HTTP_HOST and ALEPH_SUB_QUERY_HTTP_PATH if needed.
• Tools will be exposed under the server name you choose (default: aleph_shared).
• aleph_shared avoids conflicts with an existing aleph stdio entry in Codex config.
• For Claude, the shared session is passed via --mcp-config and --strict-mcp-config flags.

For even higher limits:

{
  "args": ["--enable-actions", "--workspace-mode", "any", "--tool-docs", "concise", "--timeout", "120", "--max-output", "100000"]
}

If you need stricter workspace scoping (single project only), continue below.

The Workspace Root Issue

Problem: The aleph MCP server defaults to using the current working directory as the workspace root. If you launch Cursor/VS Code from your home directory, aleph will block file operations with:

Error: Path '/path/to/your-project/aleph/mcp/local_server.py' escapes workspace root '/path/to/your-home'

Solution: Explicitly set the workspace root in your MCP configuration.

Cursor Configuration

Create or edit your Cursor MCP config:

• macOS/Linux: ~/.cursor/mcp.json
• Windows: %USERPROFILE%\.cursor\mcp.json

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": [
        "--workspace-root",
        "/path/to/your-project",
        "--enable-actions",
        "--tool-docs",
        "concise"
      ]
    }
  }
}

VS Code Configuration

Create or edit your VS Code MCP config:

• macOS/Linux: ~/.vscode/mcp.json
• Windows: %USERPROFILE%\.vscode\mcp.json

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": [
        "--workspace-root",
        "/path/to/your-project",
        "--enable-actions",
        "--tool-docs",
        "concise"
      ]
    }
  }
}

Claude Desktop Configuration

Claude Desktop auto-discovers MCP servers. To configure:

Option 1: Auto-discovery (Simplest)

aleph-rlm install claude-code

Then restart Claude Desktop - it will auto-discover aleph.

Option 2: Manual Configuration Add to your Claude settings file:

• macOS/Linux: ~/.claude/settings.json
• Windows: %USERPROFILE%\.claude\settings.json

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": [
        "--workspace-root",
        "/path/to/your-project",
        "--enable-actions",
        "--tool-docs",
        "concise"
      ]
    }
  }
}

Installing Claude Desktop Skill

For RLM workflow prompts, install the /aleph skill:

Option 1: Download docs/prompts/aleph.md and save to:

• macOS/Linux: ~/.claude/commands/aleph.md
• Windows: %USERPROFILE%\.claude\commands\aleph.md

Option 2: From installed package:

mkdir -p ~/.claude/commands
cp "$(python -c "import aleph; print(aleph.__path__[0])")/../docs/prompts/aleph.md" ~/.claude/commands/aleph.md

New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.claude\commands"
$alephPath = python -c "import aleph; print(aleph.__path__[0])"
Copy-Item "$alephPath\..\docs\prompts\aleph.md" "$env:USERPROFILE\.claude\commands\aleph.md"

This enables the /aleph command for structured reasoning workflow.

Codex CLI Configuration

Add to your Codex config:

• macOS/Linux: ~/.codex/config.toml
• Windows: %USERPROFILE%\.codex\config.toml

[mcp_servers.aleph]
command = "aleph"
args = ["--enable-actions", "--tool-docs", "concise"]

To enable actions (read_file, write_file, etc.), use:

[mcp_servers.aleph]
command = "aleph"
args = ["--workspace-root", "/path/to/your-project", "--enable-actions", "--tool-docs", "concise"]

Installing Codex Skill

For RLM workflow prompts, install the $aleph skill:

Option 1: Download docs/prompts/aleph.md and save to:

• macOS/Linux: ~/.codex/skills/aleph/SKILL.md
• Windows: %USERPROFILE%\.codex\skills\aleph\SKILL.md

Option 2: From installed package:

mkdir -p ~/.codex/skills/aleph
cp "$(python -c "import aleph; print(aleph.__path__[0])")/../docs/prompts/aleph.md" ~/.codex/skills/aleph/SKILL.md

New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.codex\skills\aleph"
$alephPath = python -c "import aleph; print(aleph.__path__[0])"
Copy-Item "$alephPath\..\docs\prompts\aleph.md" "$env:USERPROFILE\.codex\skills\aleph\SKILL.md"

This enables the $aleph command in Codex.

Installing Kimi CLI Skill

Kimi CLI searches for skills in these locations (in order):

• ~/.config/agents/skills/
• .agents/skills/ (project root)
• ~/.agents/skills/
• ~/.kimi/skills/
• ~/.claude/skills/
• ~/.codex/skills/
• .kimi/skills/ (project root)
• .claude/skills/ (project root)
• .codex/skills/ (project root)

For RLM workflow prompts, install the Aleph skill in one of the first two locations:

Option 1 (recommended, user-level):

mkdir -p ~/.config/agents/skills/aleph
cp "$(python -c "import aleph; print(aleph.__path__[0])")/../docs/prompts/aleph.md" ~/.config/agents/skills/aleph/SKILL.md

Option 2 (project-level):

mkdir -p .agents/skills/aleph
cp "$(python -c "import aleph; print(aleph.__path__[0])")/../docs/prompts/aleph.md" .agents/skills/aleph/SKILL.md

You can also override the search path with --skills-dir.

Parameters Explained

These parameters apply to aleph:

• --workspace-root <path> - The root directory for file operations (read_file, write_file, run_command, etc.)
• --workspace-mode <fixed|git|any> - Path scope for actions: fixed (workspace root only), git (any git repo), any (no path restriction)
• --enable-actions - Enable action tools (read_file, write_file, run_command, run_tests, etc.)
• --require-confirmation - Require confirm=true on all action tool calls
• --timeout <seconds> - Sandbox execution timeout (default: 60)
• --max-output <chars> - Maximum output characters from commands (default: 50000)
• --tool-docs <concise|full> - Tool description verbosity for MCP clients (default: concise). Set ALEPH_TOOL_DOCS=full for full docs.
• --max-file-size <bytes> - Maximum file size for read operations (default: 1000000000)
• --max-write-bytes <bytes> - Maximum file size for write operations (default: 100000000)

Sub-query backends

sub_query can use an API backend or a local CLI backend. When ALEPH_SUB_QUERY_BACKEND is auto (default), Aleph chooses the first available backend:

1. codex CLI - if installed
2. gemini CLI - if installed
3. claude CLI - if installed (deprioritized in MCP/sandbox contexts)
4. API - if API credentials are available (fallback)

API Configuration

The API backend uses OpenAI-compatible endpoints only. Configure with these environment variables:

Precedence: ALEPH_SUB_QUERY_URL overrides OPENAI_BASE_URL. If neither is set, Aleph uses https://api.openai.com/v1.

Quick Setup Examples

OpenAI:

export ALEPH_SUB_QUERY_API_KEY=sk-...
export ALEPH_SUB_QUERY_MODEL=your-model-name

Groq (fast inference):

export ALEPH_SUB_QUERY_API_KEY=gsk_...
export ALEPH_SUB_QUERY_URL=https://api.groq.com/openai/v1
export ALEPH_SUB_QUERY_MODEL=llama-3.3-70b-versatile

Local LLM (Ollama, LM Studio, etc.): Make sure your local server is running and the model is available before configuring the endpoint.

export ALEPH_SUB_QUERY_API_KEY=ollama  # Any non-empty value works
export ALEPH_SUB_QUERY_URL=http://localhost:11434/v1
export ALEPH_SUB_QUERY_MODEL=llama3.2

Configuration Options

Use ALEPH_SUB_QUERY_BACKEND when you want to pin a backend or bypass auto-detection; otherwise leave it unset to use the default auto selection order above.

Note: Some MCP clients don't reliably pass env vars from their config to the server process. If sub_query reports "API key not found" despite your client's MCP settings, add the exports to your shell profile:

• macOS/Linux: ~/.zshrc or ~/.bashrc
• Windows: System Environment Variables or $PROFILE in PowerShell

Then restart your terminal/client.

For a full list of options, see docs/CONFIGURATION.md.

Finding Your Workspace Root

The workspace root should be the directory containing:

• Your .git folder (for git repositories)
• Your pyproject.toml, package.json, etc.
• The root of your project

Automatic Detection: If you don't set --workspace-root, aleph will:

1. Use ALEPH_WORKSPACE_ROOT if set
2. Otherwise prefer PWD (falls back to INIT_CWD) when present
3. Check if .git exists in that directory
4. If not, search parent directories until finding .git
5. Use that directory as the workspace root

Recommended: Always set --workspace-root explicitly to avoid ambiguity. If you need to work across multiple repos in one MCP server, prefer --workspace-mode git and use absolute paths (or a broad workspace root).

Example Scenarios

Scenario 1: Python Project

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": [
        "--workspace-root",
        "/Users/yourname/projects/my-python-app",
        "--enable-actions",
        "--tool-docs",
        "concise"
      ]
    }
  }
}

Scenario 2: Monorepo

For a monorepo, set workspace to a subdirectory:

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": [
        "--workspace-root",
        "/Users/yourname/monorepo/packages/frontend",
        "--enable-actions",
        "--tool-docs",
        "concise"
      ]
    }
  }
}

Scenario 3: Remote Development

For development on remote machines:

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": [
        "--workspace-root",
        "/remote/path/to/project",
        "--enable-actions",
        "--tool-docs",
        "concise",
        "--timeout",
        "60"
      ]
    }
  }
}

Scenario 4: Increased Limits

Customize limits for your use case:

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": [
        "--workspace-root", "/path/to/project",
        "--enable-actions",
        "--tool-docs",
        "concise",
        "--timeout", "60",
        "--max-output", "100000",
        "--max-file-size", "5000000000",
        "--max-write-bytes", "500000000"
      ]
    }
  }
}

Default limits:

• Timeout: 60 seconds
• Max command output: 50,000 characters
• Max file read: 1,000,000,000 bytes (1GB)
• Max file write: 100,000,000 bytes (100MB)

Scenario 5: Any Git Repo

Allow action tools to operate in any git repo on the machine:

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": [
        "--enable-actions",
        "--tool-docs",
        "concise",
        "--workspace-mode",
        "git"
      ]
    }
  }
}

Use absolute paths in tool calls (or set --workspace-root to a broad parent) when working across repos.

Security Considerations

Actions Mode

When you enable --enable-actions, you grant aleph permission to:

• Read files - Read any file in workspace (up to 1GB by default)
• Write files - Create/modify files in workspace (up to 100MB by default)
• Run commands - Execute shell commands (30s timeout by default)
• Run tests - Execute test commands Use --workspace-mode git to limit access to git repos, or --workspace-mode any to remove path restrictions.

Confirmation Mode

Use --require-confirmation for safer operation:

{
  "args": [
    "--workspace-root",
        "/path/to/project",
        "--enable-actions",
        "--tool-docs",
        "concise",
        "--require-confirmation"
  ]
}

When enabled, all action tools require confirm=true in the call.

Adjusting Limits

Customize limits for your use case:

{
  "args": [
    "--workspace-root", "/path/to/project",
    "--enable-actions",
    "--tool-docs",
    "concise",
    "--timeout", "60",
    "--max-output", "100000",
    "--max-file-size", "5000000000",
    "--max-write-bytes", "500000000"
  ]
}

Default limits:

• Timeout: 60 seconds
• Max command output: 50,000 characters
• Max file read: 1,000,000,000 bytes (1GB)
• Max file write: 100,000,000 bytes (100MB)

Troubleshooting

"Path escapes workspace root" Error

Symptom: File operations fail with path validation error.

Cause: Workspace root not set or incorrect.

Solution: Add --workspace-root to MCP configuration with the correct path. If you intentionally want multi-repo access, use --workspace-mode git or --workspace-mode any.

Examples:

Cursor:

{
  "mcpServers": {
    "aleph": {
      "args": [
        "--workspace-root",
        "/path/to/your-project",
        "--enable-actions",
        "--tool-docs",
        "concise"
      ]
    }
  }
}

VS Code:

{
  "mcpServers": {
    "aleph": {
      "args": [
        "--workspace-root",
        "/path/to/your-project",
        "--enable-actions",
        "--tool-docs",
        "concise"
      ]
    }
  }
}

Claude Desktop:

{
  "mcpServers": {
    "aleph": {
      "args": [
        "--workspace-root",
        "/path/to/your-project",
        "--enable-actions",
        "--tool-docs",
        "concise"
      ]
    }
  }
}

Codex:

[mcp_servers.aleph]
command = "aleph"
args = ["--workspace-root", "/path/to/your-project", "--enable-actions", "--tool-docs", "concise"]

"Actions are disabled" Error

Symptom: Action tools (read_file, write_file, etc.) return "Actions are disabled."

Cause: --enable-actions flag not set.

Solution: Add --enable-actions to MCP configuration.

Examples for each client:

All clients require adding --enable-actions:

• Cursor: Add to args array
• VS Code: Add to args array
• Claude Desktop: Add to args array
• Codex CLI: Add to args array

MCP Server Not Starting

Symptom: Tools don't appear in Cursor/VS Code.

Possible causes:

1. aleph not installed: pip install "aleph-rlm[mcp]"
2. Entry point not available: Run aleph --help to test
3. Python not in PATH: Use full path to python/python3
4. Workspace root path incorrect
5. MCP client not restarted after config changes

Debug steps:

# Test if command works
aleph --help

# Check installation
pip show aleph-rlm

# Test server manually
python3 -m aleph.mcp.server --help

# Restart MCP client (Cursor/VS Code/Claude Desktop)

sub_query Timed Out

Symptom: sub_query calls fail with a timeout error.

Causes: Backend latency, large context slices, or low timeout settings.

Solution: Increase the sub-query timeout and/or reduce context size.

Examples:

# Env var
export ALEPH_SUB_QUERY_TIMEOUT=120

# CLI flag
aleph --sub-query-timeout 120

Runtime (MCP tool):

mcp__aleph__configure(sub_query_timeout=120)

If you're passing very large context slices, consider chunking (e.g., chunk(100000) + sub_query_batch).

sub_query Reports "API Key Not Found"

Symptom: sub_query tool returns "API key not found" errors despite having credentials configured.

Cause: Some MCP clients don't reliably pass env vars from their config to the server process.

Solution: Add credentials to your shell profile:

macOS/Linux (add to ~/.zshrc or ~/.bashrc):

export ALEPH_SUB_QUERY_API_KEY=sk-...
export ALEPH_SUB_QUERY_MODEL=your-model-name

Windows (add to System Environment Variables, or PowerShell $PROFILE):

$env:ALEPH_SUB_QUERY_API_KEY = "sk-..."
$env:ALEPH_SUB_QUERY_MODEL = "your-model-name"

Then restart your terminal/MCP client.

Note: This is a client-side limitation, not an aleph bug.

Other MCP Clients

Kimi CLI

Kimi CLI can manage MCP servers from the command line:

kimi mcp add --transport stdio aleph -- \
  aleph --enable-actions --tool-docs concise --workspace-root /path/to/your-project

You can also edit the MCP config directly:

• Config file: ~/.kimi/mcp.json

{
  "mcpServers": {
    "aleph": {
      "transport": "stdio",
      "command": "aleph",
      "args": ["--enable-actions", "--tool-docs", "concise", "--workspace-root", "/path/to/your-project"]
    }
  }
}

Windsurf

Windsurf uses standard MCP configuration files. Add to your MCP settings:

{
  "mcpServers": {
    "aleph": {
      "command": "aleph",
      "args": [
        "--workspace-root",
        "/path/to/your-project",
        "--enable-actions",
        "--tool-docs",
        "concise"
      ]
    }
  }
}

Cline / Continue.dev

These clients support standard MCP configuration. Check their documentation for exact file locations and format.

Generic MCP Client

If your MCP client uses a different configuration system, the key parameters are:

• Command: aleph
• Required args: --workspace-root /path/to/project
• Optional args: --enable-actions, --tool-docs <concise|full>, --require-confirmation, --timeout, etc.

Related Documentation

• REMOTE_MCP_DIAGNOSIS.md - Debugging remote MCP server issues
• README.md - Project overview and installation
• docs/CONFIGURATION.md - Full aleph configuration reference
• docs/openai.md - OpenAI-specific configuration

Support

For issues specific to MCP configuration, please check:

1. Your MCP client documentation (Cursor, VS Code, Claude Desktop, Codex, Windsurf, etc.)
2. This configuration guide
3. Remote MCP diagnosis guide

For aleph-specific bugs or feature requests, please open an issue on GitHub.