# AILEX MCP server

> Read case, schedule, task and document data from AILEX, a practice-management service for small law firms in Japan.

- Listing: https://mcp.tc/i/ailex
- Connect: use the server's own URL `https://app.ailex.co.jp/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Productivity & Projects](https://mcp.tc/c/productivity)
- Vendor: AILEX
- Homepage: <https://ailex.co.jp/>
- Docs: <https://ailex.co.jp/mcp/>

## About

AILEX is a Japanese-language practice-management SaaS for small law firms. This hosted MCP endpoint gives an assistant read-only access to a firm's AILEX v2 records, covering items such as cases, schedules, tasks and documents.

The server runs as a hosted streamable HTTP endpoint at https://app.ailex.co.jp/mcp. It requires a token issued by the user's law firm in AILEX v2, sent in the Authorization: Bearer header. Access is read-only (scope mcp:read) and limited to that firm's records. AILEX says sign-in with OAuth is being prepared and isn't available yet, so follow its official documentation for client setup.

## What it can do

- Look up cases in your AILEX account
- Check schedules and upcoming tasks
- Read documents stored for a case
- Read-only access through the mcp:read scope

## Example prompts

- "Show my open cases in AILEX."
- "What is on my AILEX schedule this week?"
- "List overdue tasks for my firm in AILEX."
- "Find documents attached to a case in AILEX."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http ailex https://app.ailex.co.jp/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
```

2. Replace the placeholder with your key before you run it, then check it with `/mcp` inside Claude Code.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Use the `mcp-remote` bridge, which keeps the key on this computer (a connector added on claude.ai with the key under **Request headers** also shows up here). Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "ailex": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.ailex.co.jp/mcp",
        "--header",
        "Authorization: Bearer <YOUR_API_KEY>"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=AILEX&connectorUrl=https%3A%2F%2Fapp.ailex.co.jp%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://app.ailex.co.jp/mcp`. Under **Request headers**, add `Authorization: Bearer <YOUR_API_KEY>` with your key from AILEX, then click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=ailex&config=eyJ1cmwiOiJodHRwczovL2FwcC5haWxleC5jby5qcC9tY3AiLCJoZWFkZXJzIjp7IkF1dGhvcml6YXRpb24iOiJCZWFyZXIgPFlPVVJfQVBJX0tFWT4ifX0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "ailex": {
      "url": "https://app.ailex.co.jp/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the key the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "ailex": {
      "type": "http",
      "url": "https://app.ailex.co.jp/mcp",
      "headers": {
        "Authorization": "Bearer ${input:api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "api-key",
      "description": "API key",
      "password": true
    }
  ]
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "ailex": {
      "serverUrl": "https://app.ailex.co.jp/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add ailex --url https://app.ailex.co.jp/mcp --bearer-token-env-var AILEX_API_KEY
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.ailex]
url = "https://app.ailex.co.jp/mcp"
bearer_token_env_var = "AILEX_API_KEY"
```

Set `AILEX_API_KEY` to your key in the shell that runs Codex.

### Gemini CLI

```bash
gemini mcp add --transport http --header "Authorization: Bearer <YOUR_API_KEY>" ailex https://app.ailex.co.jp/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "ailex": {
      "type": "http",
      "url": "https://app.ailex.co.jp/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://app.ailex.co.jp/mcp`.

## Details

- Last checked: 2026-11-17 (reachable, asks for credentials)
- Listed: 2026-10-07
- Updated: 2026-10-07

---
Source: https://mcp.tc/i/ailex (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
