Bring Policy Management
to LangChain
Learn how to connect Berg System CRM to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Berg System CRM through native MCP adapters. Connect 12 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Berg System CRM MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Berg System CRM queries for multi-turn workflows
Berg System CRM in LangChain
Berg System CRM and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Berg System CRM to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters