Skip to main content
Glama
mcp-123bail
by lydstyl
README.md
# mcp-123bail

[Model Context Protocol](https://modelcontextprotocol.io) (MCP) server for **123bail / Dokimo** — self-hosted rental management (baux, locataires, loyers, quittances).

Give your AI agent (Claude Desktop, Cursor, Hermes, …) direct access to your rental portfolio: list tenants, find leases, record payments, create leases, and generate rent receipt PDFs (quittances de loyer).

## Features

| Tool | Description |
|---|---|
| `list_landlords` | All landlords with contact info |
| `get_properties_by_landlord` | Properties of a landlord |
| `get_tenants_by_landlord` | Tenants linked to a landlord |
| `search_tenants` | Search tenants by name / email |
| `find_leases_by_tenant` | Leases of a tenant |
| `get_active_leases` | All active leases |
| `add_payment` | Record a rent payment |
| `get_payment_summary_by_landlord` | Due / paid / balance over N months |
| `create_lease` | Create a new lease (bail) |
| `generate_receipt` | Rent receipt PDF (quittance) as base64 |

## Requirements

- Node.js ≥ 20
- A Dokimo / 123bail instance with **API keys** enabled (Settings → API keys → create a `mcp_…` key)

## Install

### Claude Desktop / any MCP client

```json
{
  "mcpServers": {
    "123bail": {
      "command": "npx",
      "args": ["github:lydstyl/123bail-mcp"],
      "env": {
        "DOKIMO_URL": "https://your-dokimo-instance.example.com",
        "DOKIMO_API_KEY": "mcp_xxx"
      }
    }
  }
}
```

### From source

```bash
git clone https://github.com/lydstyl/123bail-mcp.git
cd 123bail-mcp
npm install && npm run build
DOKIMO_URL=https://your-instance DOKIMO_API_KEY=mcp_xxx node dist/index.js
```

## Security

The server only sends your `DOKIMO_API_KEY` to the URL in `DOKIMO_URL`. Revoke a key anytime from the app — revocation is instant.

## License

MIT

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation4/5

Most tools are clearly scoped to a distinct resource+action (landlords, properties, tenants, leases, payments, receipts). The only mild overlap is between find_leases_by_tenant and get_active_leases when a tenant has active leases, but the descriptions make the distinction clear enough.

Naming Consistency3/5

All tools use snake_case verb_noun, but the read operations mix four different verbs: find, list, search, and get (e.g., list_landlords vs get_tenants_by_landlord vs search_tenants vs find_leases_by_tenant). This verb inconsistency is readable but breaks a predictable pattern.

Tool Count5/5

Ten tools is squarely in the well-scoped range. Each tool maps to a meaningful operation across the rental domain (properties, tenants, leases, payments, receipts) without obvious filler.

Completeness3/5

Core lifecycle is partly covered with create_lease and add_payment, but there are notable gaps: no update/terminate lease, no delete/update payment, no get_single_lease or get_tenant (only search/list variants), and payment visibility is limited to a per-landlord summary.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues