Mirlo MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIRLO_API_KEY | Yes | Your Mirlo API key. Get it at app.mirlo.com |
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 |
|---|---|
| mirlo_list_dealsA | List deals/opportunities with optional filters. Returns paginated results with total count. |
| mirlo_get_dealA | Get a deal by ID with full details including stage times, contacts, and conversations. |
| mirlo_create_dealB | Create a new deal/opportunity in a pipeline. |
| mirlo_update_dealC | Update an existing deal. Only provided fields are updated. |
| mirlo_move_deal_stageB | Move a deal to a different pipeline stage. |
| mirlo_list_contactsC | List contacts with optional search and filters. |
| mirlo_get_contactA | Get a contact by ID. |
| mirlo_create_contactB | Create a new contact. |
| mirlo_list_accountsC | List accounts/companies with optional filters. |
| mirlo_create_accountC | Create a new account/company. |
| mirlo_list_ticketsC | List support tickets with filters. |
| mirlo_create_ticketB | Create a support ticket. |
| mirlo_list_tasksA | List tasks with filters. Supports filtering by assignee, status, due date, and associated entities. |
| mirlo_create_taskC | Create a task, optionally associated to a deal, ticket, contact, or account. |
| mirlo_complete_taskB | Mark a task as completed. |
| mirlo_list_pipelinesA | List all pipelines with their stages. Useful for getting pipeline/stage IDs before creating deals. |
| mirlo_send_messageC | Send a WhatsApp or SMS message to a phone number. |
| mirlo_send_templateC | Send a pre-approved WhatsApp template message. |
| mirlo_list_conversationsC | List recent conversations across channels. |
| mirlo_list_callsC | List phone calls with filters. |
| mirlo_get_call_transcriptA | Get the AI-generated transcript of a phone call. |
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 21 tools
Each tool targets a distinct action on a specific entity (e.g., create contact vs. list contacts, send message vs. send template). No two tools have overlapping purposes, and descriptions clearly differentiate them.
All tools follow a consistent 'mirlo_verb_noun' pattern with snake_case (e.g., mirlo_create_contact, mirlo_list_deals). No mixing of conventions or styles.
21 tools is slightly above the typical 3-15 range, but the CRM/communications domain covers many entities (accounts, contacts, deals, tasks, tickets, calls, messages), so the count is reasonable and each tool earns its place.
The tool set covers core CRUD for deals and tasks, but lacks update for contacts, accounts, and tickets, and lacks delete operations entirely. These gaps may cause agent failures in workflows that require full lifecycle management.