Custify MCP Server

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:

• Churned accounts: {"fieldName":"churned","fieldType":"Boolean","filterType":"true"}

• Name contains: {"fieldName":"name","fieldType":"String","filterType":"contains","filterValue":"acme"}

• Health score > 50: {"fieldName":"metrics.health_scores.<score_id>","fieldType":"Number","filterType":"greater","filterValue":"50"}

• In segment: {"fieldName":"metrics.health_scores.<score_id>","fieldType":"Segment","filterType":"is_any_of","filterValue":["<segment_id>"]}

Get detailed information about a specific Custify account/company by ID.

Search Custify accounts/companies by name or domain.

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 contacts/people associated with a Custify account.

Get detailed information about a specific Custify contact by ID.

Get health scores for a specific Custify account, including global and individual score breakdowns.

Get usage/event data for a Custify account, optionally filtered by event name and date range.

Get historical health score values/trends over time for a specific health score metric. Optionally filter by account.

[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 all segments that a specific Custify account belongs to.

Create a note on a Custify account.

Create a task associated with a Custify account. Note: assignee_id must be a Custify user ObjectId (not an email address).

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 attribute fields on a Custify account or contact.