Skip to main content
Glama
infolegalge

legal.ge MCP Server

Official
README.md
# legal.ge MCP server

Find verified legal specialists in Georgia from inside Claude Desktop, Cursor, or any [Model Context Protocol](https://modelcontextprotocol.io/) client.

This server wraps the public [legal.ge Ask API](https://legal.ge/api/openapi.json) as MCP tools. Ask in natural language; get matched practice areas plus ranked verified specialists with their profile URLs.

## What it does

Exposes two tools:

- **`find_legal_specialists`** — describe a legal situation in natural language; get matched practice areas, specific services, and a ranked list of verified specialists, each with a profile URL on legal.ge.
- **`classify_legal_intent`** — same matcher without the specialist lookup. Returns just the matched categories, useful when you want to identify the legal domain before deciding next steps.

Both tools support Georgian (`ka`), English (`en`), and Russian (`ru`). The matcher handles colloquial phrasings, legal jargon, and cross-script abbreviations (AML, KYC, MLC, ICC, etc.).

## Trust contract

- **Verified profiles only.** Every specialist returned is `verification_status='verified'` on legal.ge. Many are registered with the Georgian Bar Association — check `professional_orgs` on each result.
- **Contact info is opt-in.** `contact.email` and `contact.phone` are populated only when the specialist has chosen to publish them. Otherwise null — the user signs in on legal.ge to send a message.
- **Read-only.** This server cannot create inquiries, bookings, or any other side effects. It only queries.
- **No keys required.** The legal.ge Ask API is public; rate-limited per IP.

## Installation

### Claude Desktop

Edit your `claude_desktop_config.json`:

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

Add the legal.ge entry under `mcpServers`:

```json
{
  "mcpServers": {
    "legal-ge": {
      "command": "npx",
      "args": ["-y", "@legalge/mcp"]
    }
  }
}
```

Restart Claude Desktop. The tools will appear in any conversation, callable when you ask about Georgian legal questions.

### Cursor

Add to `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (per-project):

```json
{
  "mcpServers": {
    "legal-ge": {
      "command": "npx",
      "args": ["-y", "@legalge/mcp"]
    }
  }
}
```

### Other MCP-compatible clients

Any client that supports stdio-transport MCP servers can use this. Configuration shape:

- Command: `npx`
- Args: `["-y", "@legalge/mcp"]`
- Transport: stdio
- Optional env: `LEGALGE_BASE_URL` (defaults to `https://legal.ge`)

## Example conversations

After installing, try asking Claude (or any MCP-aware agent):

> "Find me a Georgian lawyer who handles eviction defense for tenants in Tbilisi."

> "I was just laid off in Georgia without notice. Who can help me?"

> "ვინ შემიძლია მქონდეს ბინის ნასყიდობის ხელშეკრულების შესადგენად?"

The agent will call `find_legal_specialists` with the appropriate locale and surface verified specialists by name + profile URL + practice area.

## Development

```bash
# install dependencies
npm install

# run locally against legal.ge
npm run dev

# point at staging
LEGALGE_BASE_URL=https://staging.legal.ge npm run dev

# build
npm run build
```

## Configuration

| Env var | Default | Purpose |
|---|---|---|
| `LEGALGE_BASE_URL` | `https://legal.ge` | Override the API endpoint (e.g. for local testing) |

## API reference

The underlying HTTP API is documented at <https://legal.ge/api/openapi.json>. This MCP server is a thin wrapper — you can also call the API directly without MCP if you prefer.

## License

MIT — see [LICENSE](LICENSE).

## About legal.ge

[legal.ge](https://legal.ge) is the verified directory of legal specialists in Georgia (the country). Trilingual platform (Georgian, English, Russian). Browse practice areas, find lawyers and law firms, request consultations.

See [legal.ge/llms.txt](https://legal.ge/llms.txt) for the AI-agent contract.

TDQS

A4.1/5.0

Scored across 2 tools

Disambiguation4/5

The two tools have distinct primary purposes: one returns specialist recommendations, the other only classifies legal intent. However, both return matched practice areas, which could cause some confusion if an agent only needs classification and sees the specialist tool as a heavier version.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern: 'find_legal_specialists' and 'classify_legal_intent'. The naming is clear, predictive, and uses the same structural style.

Tool Count3/5

With only two tools, the server feels minimal. While the scope is narrow (legal specialist matching and intent classification), two tools are on the border of being too thin for a general-purpose legal assistant.

Completeness4/5

The server covers the two core operations described in its purpose: classifying legal intent and finding specialists. A minor gap is the lack of a tool to fetch detailed specialist profiles, but the returned URLs serve as a workaround for the user to access full information.

Maintenance

ActivitySlowing
ResponsivenessNo issues