mcp-123bail
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOKIMO_URL | Yes | The URL of your Dokimo / 123bail instance (e.g., https://your-dokimo-instance.example.com). The server only sends your DOKIMO_API_KEY to this URL. | |
| DOKIMO_API_KEY | Yes | API key for your Dokimo / 123bail instance (create one in Settings → API keys; it starts with 'mcp_…' and can be revoked anytime). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_landlordsB | List all landlords with contact information |
| get_properties_by_landlordA | List all properties (rental units) of a landlord, with lease counts |
| get_tenants_by_landlordB | List all tenants (email, phone) linked to a landlord via their properties and leases |
| search_tenantsB | Search tenants by name, first name, or email |
| find_leases_by_tenantB | Find all leases of a tenant by tenant ID, name, or email |
| get_active_leasesA | List all currently active leases (with tenant and property details) |
| add_paymentC | Record a rent payment for a lease |
| 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) |
| create_leaseC | Create a new lease (bail) for a property and one or more tenants |
| generate_receiptA | Generate the rent receipt PDF (quittance de loyer) for a lease and a month. Returns the PDF as base64. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
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.
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.
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.
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.