Bring Outbound Sales
to LangChain
Learn how to connect FirstQuadrant to LangChain 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 FirstQuadrant MCP Server?
Connect your FirstQuadrant account to any AI agent and take full control of your B2B sales pipeline and contact enrichment workflows through natural conversation.
What you can do
- Lead Orchestration — List and manage your complete database of leads and contacts, including retrieving detailed metadata and performing search lookups programmatically
- AI Enrichment — Trigger autonomous AI workflows to gather deep context about a lead from external sources and update contact profiles automatically
- Campaign Management — Access available sales sequences and enroll contacts into personalized email campaigns directly through your agent
- Schema Intelligence — Explore and manage your custom property schema to ensure all sales data is perfectly structured for AI analysis
- Activity Monitoring — Monitor the complete log of sales activities, including emails, calls, and AI-driven tasks in real-time
How it works
1. Subscribe to this server
2. Retrieve your API Key and Organization ID from FirstQuadrant (Settings > Developer Settings)
3. Start managing your B2B sales pipeline from Claude, Cursor, or any MCP client
No more manual contact research or complex campaign toggling. Your AI acts as your dedicated sales operations coordinator.
Who is this for?
- Sales Development Reps (SDRs) — instantly identify top leads and trigger enrichment workflows using natural language
- Account Managers — retrieve full interaction histories and verify contact details without leaving your workspace
- Growth Teams — automate lead discovery and scale personalized outreach through simple AI queries
Built-in capabilities (8)
Add contact to a campaign
Create a new lead/contact
Trigger AI enrichment for a contact
Get contact profile details
List sales activities
List sales campaigns/sequences
Supports advanced filtering by email or created date. List FirstQuadrant contacts
List custom properties schema
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with FirstQuadrant through native MCP adapters. Connect 8 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 FirstQuadrant 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 FirstQuadrant queries for multi-turn workflows
FirstQuadrant in LangChain
FirstQuadrant and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect FirstQuadrant 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 FirstQuadrant in LangChain
The FirstQuadrant 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 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
FirstQuadrant for LangChain
Every tool call from LangChain to the FirstQuadrant 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 Organization ID in FirstQuadrant?
Log in to your FirstQuadrant dashboard and navigate to Settings > Developer Settings. Your unique Organization ID will be listed there.
Can the agent update custom properties?
Yes! Use the create_contact or enrich_contact_ai tools to manage standard and custom data points defined in your property schema.
How does AI enrichment work through the agent?
The enrich_contact_ai tool triggers FirstQuadrant's autonomous research engine to scan public sources and update the contact record with high-fidelity insights.
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