Bring Lead Management
to LangChain
Learn how to connect Richards CRM to LangChain and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Richards CRM MCP Server?
Connect your Richards Building Supply CRM account to any AI agent and take full control of your exterior contracting orchestration through natural conversation. Powered by the Construct CRM engine, this integration allows you to retrieve lead metadata, manage project lifecycles, and orchestrate material orders directly from your chat interface.
What you can do
- Lead & Prospect Orchestration — List all managed leads and retrieve detailed profile metadata, including creating new contacts programmatically to ensure your pipeline is always synchronized.
- Project & Job Lifecycle Management — Access and monitor active projects and retrieve detailed technical metadata directly from the AI interface to keep your exterior jobs on track.
- Estimating & Proposals Intelligence — Access project estimates and monitor proposal statuses to ensure your bidding process is always optimized via natural language.
- Material Ordering & Invoice Control — List and retrieve order metadata and invoices to maintain a clear overview of your supply chain and business expenses.
- Operational Monitoring — Track employee assignments and manage company profile metadata using simple AI commands.
How it works
1. Subscribe to this server
2. Enter your Richards CRM API Key from your account settings
3. Start managing your contracting workflows from Claude, Cursor, or any MCP-compatible client
No more manual order tracking or switching between Material and CRM apps. Your AI acts as a dedicated project coordinator or operations lead.
Who is this for?
- Exterior Contractors & Foremen — quickly retrieve project details and monitor lead status without switching apps.
- Operations Managers — automate the management of material orders and track project history via natural conversation.
- Sales Teams — streamline the retrieval of estimates and monitor proposal health directly within the chat.
Built-in capabilities (11)
Create a new lead
Get company profile details
Get details for a specific lead
Get details of a specific project
List all employees
List all estimates
List all invoices
List all leads
List all purchase orders
List all projects
List all proposals
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Richards CRM through native MCP adapters. Connect 11 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 Richards 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 Richards CRM queries for multi-turn workflows
Richards CRM in LangChain
Richards CRM and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Richards 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 Richards CRM in LangChain
The Richards 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 11 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
Richards CRM for LangChain
Every tool call from LangChain to the Richards CRM MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the details and status for a specific project just by providing its ID?
Yes! Use the get_project tool with the Project ID. Your agent will respond with complete metadata, including job status, linked leads, and material requirements in seconds.
How do I find my Richards CRM API Key?
Log in to your Richards CRM account, navigate to the integration or API settings section, and you will find your unique secret API key there.
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