Bring Customer Success
to Pydantic AI
Learn how to connect Custify to Pydantic AI and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Custify MCP Server?
Connect your Custify customer success account to any AI agent and simplify how you manage your product users, track account health, and monitor churn risk through natural conversation.
What you can do
- User & Company Oversight — List all managed people and organizations and retrieve detailed metadata and health scores.
- Health Monitoring — Query health score metrics and values to identify at-risk customers and churn signals instantly.
- Event Tracking — Record custom user actions and events programmatically to feed your success analytics.
- Segment Analysis — List and query defined customer segments to understand your user distribution.
- CRM Control — Create new person records and update profile data directly via AI commands.
- Engagement Insights — Fetch engagement history and metadata for individual accounts directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Custify API Key (found in your account settings)
3. Start managing your customer success lifecycle from Claude, Cursor, or any MCP client
Who is this for?
- Customer Success Managers (CSMs) — quickly check account health and track recent user events via simple AI queries.
- Success Operations — monitor segment distributions and verify company metadata directly from the workspace.
- Product Teams — track custom feature adoption events and monitor user profile quality via the AI assistant.
Built-in capabilities (8)
Create a new person record
Get details for a specific company
Get details for a specific person
List customer companies
List customer health scores
List product users (people)
List user segments
Track a custom event
Why Pydantic AI?
Pydantic AI validates every Custify tool response against typed schemas, catching data inconsistencies at build time. Connect 8 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.
- —
Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application
- —
Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your Custify integration code
- —
Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors
- —
Dependency injection system cleanly separates your Custify connection logic from agent behavior for testable, maintainable code
Custify in Pydantic AI
Custify and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Custify to Pydantic AI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Custify in Pydantic AI
The Custify 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. All 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Pydantic AI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Custify for Pydantic AI
Every tool call from Pydantic AI to the Custify MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check the health score of a company via AI?
Yes! Use the get_company_details tool and provide the Company ID. Your agent will retrieve the current health score, risk status, and account metadata.
How do I track a custom user event using the agent?
Use the track_user_event action. Provide the User ID and the Event Name. You can also pass a JSON object with additional attributes for the action.
Is it possible to see my defined customer segments via AI?
Absolutely. Use the list_user_segments query. The agent will retrieve the complete list of segments configured in your Custify account.
How does Pydantic AI discover MCP tools?
Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.
Does Pydantic AI validate MCP tool responses?
Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.
Can I switch LLM providers without changing MCP code?
Absolutely. Pydantic AI abstracts the model layer. your Custify MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.
MCPServerHTTP not found
Update: pip install --upgrade pydantic-ai