Monica CRM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Optional pino log level (fatal|error|warn|info|debug|trace|silent) | info |
| MONICA_BASE_URL | No | The base URL of your Monica CRM instance (defaults to https://app.monicahq.com; change for self-hosted instances) | https://app.monicahq.com |
| MONICA_API_TOKEN | Yes | Your Monica CRM API token | |
| MONICA_TOKEN_TYPE | No | The type of token authentication to use (one of: bearer (default), apiKey, legacy) | bearer |
| MONICA_USER_TOKEN | No | Required only when MONICA_TOKEN_TYPE=legacy |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| monica_search_contactsA | Search Monica CRM contacts by name, nickname, or email. Returns contact IDs and basic info. Use the returned ID with other tools to get details or make updates. |
| monica_manage_contactA | Advanced contact management tool with section-based operations. Set section to "summary" to retrieve full contact details, "profile" for contact creation/updates, "field" for managing contact fields (email/phone/etc), or "address" for address management. For simpler operations, prefer the dedicated wrapper tools: monica_manage_contact_profile, monica_manage_contact_field, or monica_manage_contact_address. |
| monica_list_contactsA | Retrieve a paginated list of contacts without requiring a search query. Choose the detail level (minimal/basic/expanded/full) and optional filters (gender, tags, communication details). |
| monica_manage_contact_profileA | Create, update, or delete a contact profile. Use this simplified tool instead of monica_manage_contact when working with contact profiles. Provide firstName, lastName, and optional fields like nickname, description, genderName, birthdate, etc. Gender is optional - omit if unknown. |
| monica_manage_contact_fieldB | List, get, create, update, or delete contact fields like email addresses, phone numbers, social media handles, etc. Use this simplified tool instead of monica_manage_contact when managing contact fields. Provide contactId and fieldPayload with data and contactFieldTypeName (e.g., "Email", "Phone"). |
| monica_manage_contact_addressA | List, get, create, update, or delete contact addresses. Use this simplified tool instead of monica_manage_contact when managing addresses. Provide contactId and addressPayload with name, street, city, province, postalCode, and countryName (country lookup is automatic). |
| monica_manage_contact_field_typeC | List, inspect, create, update, or delete contact field types (e.g., Email, Twitter, Instagram). Use this when you need new field types for social accounts or custom data. |
| monica_manage_contact_tagsA | List, append, or remove tags on a specific contact. Use tagNames to add new/existing tags, or tagIds/tagNames to remove associations. |
| monica_manage_activity_typeA | List, inspect, create, update, or delete Monica activity types (e.g., Meeting, Coffee, Meal). Use this to expand the catalog with custom activity names before logging activities. |
| monica_manage_activityC | List, inspect, create, update, or delete activities (meetings, events, shared interactions). Provide either activityTypeId or activityTypeName. |
| monica_manage_conversationC | List, inspect, create, update, delete, or manage messages inside Monica conversations. Provide either contactFieldTypeId or contactFieldTypeName for the channel. |
| monica_manage_callC | List, inspect, create, update, or delete logged phone calls. Use this to capture quick notes about conversations with contacts. |
| monica_manage_groupA | List, inspect, create, update, or delete contact groups. Use this to organize contacts into named collections (e.g., "Family", "Travel buddies"). |
| monica_manage_relationshipB | List, inspect, create, update, or delete relationships between contacts. Provide relationshipTypeId or relationshipTypeName to identify the connection. |
| monica_manage_tagC | List, inspect, create, update, or delete tags. Tags allow you to group and categorize contacts. |
| monica_manage_noteA | List, inspect, create, update, or delete notes attached to a contact. Use this to capture or revise journal snippets. |
| monica_manage_task_reminderC | List, inspect, create, update, or delete Monica tasks and reminders. Choose itemType="task" for to-dos or itemType="reminder" for stay-in-touch nudges. |
| monica_manage_financial_recordA | List, inspect, create, update, or delete gifts and debts. Use recordType="gift" for presents, recordType="debt" for money owed. |
| monica_manage_mediaC | List, inspect, upload, or delete documents and photos stored in Monica. Use mediaType to pick the resource. |
| monica_browse_metadataB | Inspect Monica lookup catalogs (genders, countries, contact field types, activity types, relationship types). Helpful when you need to confirm the exact name/ID before performing other actions. |
| monica_health_checkB | Verify that the configured Monica credentials work. |
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
Most tools have distinct purposes targeting specific Monica CRM resources (e.g., contacts, activities, tags), with clear boundaries. However, some overlap exists between monica_manage_contact and its simplified wrapper tools (monica_manage_contact_profile, monica_manage_contact_field, monica_manage_contact_address), which could cause confusion about when to use the advanced versus simplified versions. Descriptions help clarify this, but the redundancy introduces minor ambiguity.
All tool names follow a consistent pattern: 'monica_' prefix, then a verb (e.g., browse, list, manage, search), and a noun or noun phrase (e.g., metadata, contacts, activity). This verb_noun structure is predictable and readable throughout the set, with no deviations in style or convention.
With 21 tools, the count is slightly high but reasonable for a comprehensive CRM server covering contacts, activities, tags, media, and other entities. Each tool appears to serve a specific function, though some simplification (e.g., merging wrapper tools) could reduce the number without losing functionality. It's well-scoped for the domain but borders on feeling heavy.
The tool set provides complete CRUD/lifecycle coverage for Monica CRM's core domain, including contacts, activities, tags, relationships, media, notes, and more. There are no obvious gaps; tools like monica_browse_metadata and monica_health_check support setup and validation, while dedicated tools handle all major operations without dead ends.