Bring Policy Management
to Claude Desktop
Learn how to connect Berg System CRM to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect Berg System CRM to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Berg System CRM in Claude Desktop
Berg System CRM and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Berg System CRM to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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 Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.