Custify MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port (only used with streamable-http transport) | 3000 |
| MCP_TRANSPORT | No | Transport mode: stdio or streamable-http | stdio |
| CUSTIFY_API_KEY | Yes | Your Custify API key | |
| CUSTIFY_API_URL | No | Custom API base URL (for different clusters) | https://api.custify.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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List Custify accounts/companies with optional filters. Filters use Custify's filter format: each filter is an object with fieldName, fieldType, filterType, and filterValue. Use the list_attributes tool to discover available fields and their types. Common examples:
|
| get_accountC | Get detailed information about a specific Custify account/company by ID. |
| search_accountsC | Search Custify accounts/companies by name or domain. |
| list_attributesA | List all available company/account attributes that can be used for filtering and sorting. Returns field names, display names, and field types. Use this to discover which fields are available before building filters for list_accounts. |
| get_contactsC | Get contacts/people associated with a Custify account. |
| get_contactC | Get detailed information about a specific Custify contact by ID. |
| get_health_scoresB | Get health scores for a specific Custify account, including global and individual score breakdowns. |
| get_usage_dataC | Get usage/event data for a Custify account, optionally filtered by event name and date range. |
| get_usage_trendsB | Get historical health score values/trends over time for a specific health score metric. Optionally filter by account. |
| get_alertsB | [V1 LIMITATION: This tool may not work as expected — the underlying alerts API has limited support. Out of scope for the current version.] Get alerts/signals from Custify for a specific account, optionally filtered by status. |
| get_segment_membershipC | Get all segments that a specific Custify account belongs to. |
| create_noteC | Create a note on a Custify account. |
| create_taskC | Create a task associated with a Custify account. Note: assignee_id must be a Custify user ObjectId (not an email address). |
| run_playbookA | Trigger a manually-started Custify playbook on a specific account. Only playbooks with trigger type "manually started" can be triggered via the API; segment-based and event-based playbooks run automatically and cannot be triggered this way. |
| update_custom_fieldsC | Update custom attribute fields on a Custify account or contact. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| segments | List of all Custify segments (smart lists) for companies |
| playbooks | List of all Custify playbooks for companies |
| health-score-definitions | List of all Custify health score definitions and their configurations |
TDQS
Scored across 15 tools
Most tools have distinct purposes targeting specific Custify resources like accounts, contacts, notes, tasks, alerts, health scores, segments, usage data, and playbooks. However, list_accounts and search_accounts have some functional overlap in retrieving accounts, though list_accounts offers richer filtering while search_accounts is simpler by name/domain.
Tool names follow a highly consistent verb_noun pattern throughout, such as create_note, get_account, list_attributes, run_playbook, and update_custom_fields. All tools use snake_case with clear, predictable naming conventions.
With 15 tools, this server is well-scoped for managing a Custify CRM platform. It covers core operations like account/contact management, data retrieval, and automation without being overwhelming or sparse.
The toolset provides strong coverage for account and contact management, including CRUD-like operations (e.g., get, list, update, create notes/tasks) and advanced features like health scores, segments, and playbooks. Minor gaps include no direct delete operations and limited alert functionality as noted, but agents can handle most workflows effectively.