How do I get a Custify API Key?

Log in to your Custify account, navigate to **Settings > API**, and you will find your API Key there. Ensure you have the necessary permissions to manage customer data.

Can the agent update health scores?

This integration currently focuses on listing and retrieving data. Health scores are typically calculated automatically by Custify based on usage and interaction data.

Does Custify support B2B company tracking?

Yes, Custify allows you to track both individual customers and company-level entities, which is fully supported by this integration.

Custify MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Custify
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Custify through Vinkius, pass the Edge URL in the `mcps` parameter and every Custify tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Custify Specialist",
    goal="Help users interact with Custify effectively",
    backstory=(
        "You are an expert at leveraging Custify tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Custify "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Custify MCP Server

Integrate Custify, the comprehensive customer success platform, directly into your AI workflow. Monitor customer health, track churn risks, and manage your success tasks and notes using natural language.

When paired with CrewAI, Custify becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Custify tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Customer Oversight — List and retrieve detailed profiles, health scores, and churn probabilities for all customers.
Company Monitoring — Access company-level metrics and success data to manage B2B relationships effectively.
Success Task Management — List and track open tasks and internal CRM notes for your accounts.
KPI Discovery — Explore key performance indicators and metrics defined in your Custify account.

The Custify MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Custify to CrewAI via MCP

Follow these steps to integrate the Custify MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Custify

Why Use CrewAI with the Custify MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Custify through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Custify + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Custify MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Custify for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Custify, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Custify tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Custify against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Custify MCP Tools for CrewAI (10)

These 10 tools become available when you connect Custify to CrewAI via MCP:

create_customer_profile

Resolves the newly generated customer ID and validation status. Mutates the customer database state. Create a new customer profile in Custify

get_company_details

Resolves organizational attributes and health metrics. Touches the core company repository. Get detailed settings and metrics for a specific company

get_customer_details

Resolves health scores, recent activity, and segment membership. Interacts with the behavioral analytics boundary. Get full profile and health metrics for a specific customer

list_companies

Resolves company IDs, domain information, and association metrics. Touches the account-level organization boundary. List all companies in Custify

list_customer_kpis

Resolves metric definitions and threshold values. Interacts with the performance monitoring boundary. List key performance indicators defined in the account

list_customer_notes

Resolves note content and authorship metadata. Touches the internal communications boundary. List internal CRM notes for a specific customer

list_customer_success_tasks

Resolves task priority, status, and assigned owners. Interacts with the workflow automation boundary. List open and completed customer success tasks

list_customers

Resolves properties such as customer ID, name, email, and lifecycle stage. Interacts with the customer success management boundary. List all customers in Custify

list_people

Resolves contact details and account associations. Touches the relationship management boundary. List all people associated with accounts

search_customers_by_keyword

Resolves matching customer profiles based on name or email. Touches the search and indexing boundary. Search for customers by name or email

Example Prompts for Custify in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Custify immediately.

"List all customers with a health score below 50."

"Show me the success tasks for company 'Alpha Corp'."

"Search for customer 'john.doe@example.com'."

Troubleshooting Custify MCP Server with CrewAI

Common issues when connecting Custify to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Custify + CrewAI FAQ

Common questions about integrating Custify MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.