Skip to main content
Glama
mcp-123bail
by lydstyl

mcp-123bail

Model Context Protocol (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

Related MCP server: TenantCloud MCP Server

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

{
  "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

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

Available Tools

10 tools
add_paymentC

Record a rent payment for a lease

Inputs: amount (required), lease_id (required), payment_date (required), notes.

create_leaseC

Create a new lease (bail) for a property and one or more tenants

Inputs: startDate (required), tenantIds (required), propertyId (required), rentAmount (required), +5 more.

find_leases_by_tenantB

Find all leases of a tenant by tenant ID, name, or email

Inputs: tenant (required).

generate_receiptA

Generate the rent receipt PDF (quittance de loyer) for a lease and a month. Returns the PDF as base64.

Inputs: month (required), leaseId (required).

get_active_leasesA

List all currently active leases (with tenant and property details)

Inputs: no named parameters.

get_payment_summary_by_landlordA

Payment summary over the last N months for the active leases of a landlord (per-lease monthly due/paid/balance)

Inputs: landlord (required), months.

get_properties_by_landlordA

List all properties (rental units) of a landlord, with lease counts

Inputs: landlord (required).

get_tenants_by_landlordB

List all tenants (email, phone) linked to a landlord via their properties and leases

Inputs: landlord (required).

list_landlordsB

List all landlords with contact information

Inputs: no named parameters.

search_tenantsB

Search tenants by name, first name, or email

Inputs: query (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to operate property management systems via natural language, covering repair orders, owner info, payments, notices, and inspections. Features a full agentic workflow with human-in-the-loop and observability.
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage a Lendlord landlord account through its private JSON API, covering properties, documents, tenants, maintenance reports, tasks and alerts, rent, transactions, compliance, and filing emails against properties. Supports local stdio or hosted HTTP transports with credential-based login, optional TOTP 2FA, read-only mode, and once-per-session write confirmation.
      40
      26 npm
      MIT