Bring Policy Management
to CrewAI
Learn how to connect Berg System CRM to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Berg System CRM MCP Server?
Connect your Berg System account to any AI agent and take full control of your insurance agency operations and customer relationship workflows through natural conversation.
What you can do
- Customer Orchestration — List and search through individual and corporate client directories programmatically, retrieving detailed high-fidelity profile metadata and contact history
- Sales Pipeline Intelligence — Monitor sales opportunities and track deal progress across your entire agency to maintain a perfectly coordinated sales cycle
- Insurance Policy Monitoring — Retrieve active insurance policies and access high-fidelity document metadata directly through your agent to oversee coverage status
- Infrastructure Monitoring — Access system employee lists and manage CRM-related tasks programmatically for instant operational reporting
- Relationship Intelligence — Retrieve complete historical interactions for any record to maintain high-fidelity oversight of your agency's relationship ecosystem
How it works
1. Subscribe to this server
2. Retrieve your Tenant ID and OAuth Access Token from your Berg System instance
3. Start managing your insurance business from Claude, Cursor, or any MCP client
No more manual toggling between CRM tabs or digging through paper policy files. Your AI acts as your dedicated agency administrator and sales coordinator.
Who is this for?
- Insurance Agents — instantly retrieve client coverage details and update lead statuses using natural language commands
- Agency Managers — monitor team productivity and track agency-wide sales trends without leaving your workspace
- Operations Leads — automate the oversight of corporate client directories and task management through simple AI queries
Built-in capabilities (12)
Verify Berg System API status
Add a new business client
Supports forceAdd to bypass duplicates. Add a new customer
Get details for a customer
Retrieve custom sales fields
List corporate clients
List CRM customers
List active tasks and reminders
List active insurance policies
List sales records
List uploaded documents
List organization employees
Why CrewAI?
When paired with CrewAI, Berg System CRM becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Berg System CRM tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Berg System CRM in CrewAI
Berg System CRM and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Berg System CRM to CrewAI 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 Berg System CRM in CrewAI
The Berg System CRM 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 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI 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
Berg System CRM for CrewAI
Every tool call from CrewAI to the Berg System CRM MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Berg System Tenant ID?
Your Tenant ID is the unique identifier for your agency instance, found in your Berg System sub-domain (e.g., yourcompany.bergsystem.pl).
Can I check for duplicates via AI?
Yes! The system automatically checks for existing records, and you can use the forceAdd parameter in creation tools to decide how to handle them.
How do I retrieve insurance policies?
Use the list_insurance_policies tool to retrieve a comprehensive summary of all active policies managed within your CRM programmatically.
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.
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.