Compatible with every major AI agent and IDE
What is the CRM PipeRun MCP Server?
Connect your PipeRun CRM account to any AI agent to streamline your sales operations through natural conversation.
What you can do
- Activity Management — List, create, update, and delete tasks or appointments to keep your sales momentum.
- File Handling — Upload documents to deals, persons, or companies, and manage existing attachments effortlessly.
- Activity Types — Explore and categorize your interactions using specific activity types defined in your CRM.
- Detailed Inspection — Retrieve full metadata for specific activities or files to get the context you need.
How it works
- Subscribe to this server
- Enter your PipeRun API Token
- Start managing your CRM from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Sales Representatives — quickly update meeting notes and task statuses without leaving your workflow.
- Sales Managers — monitor team activities and file attachments across deals.
- Operations Teams — automate the organization of sales documents and activity logging.
Built-in capabilities (11)
Create a new activity
Delete an activity
Delete a file from PipeRun
Get details for a specific activity
Get details for a specific activity type
Get details for a specific file
List activities (tasks and appointments)
List all activity types
Supports pagination and filtering. List files attached to deals, persons, or companies
Update an existing activity
Requires base64 encoded file content. Upload a file to a deal, person, or company
Why CrewAI?
When paired with CrewAI, CRM PipeRun becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call CRM PipeRun 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
CRM PipeRun in CrewAI
CRM PipeRun and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect CRM PipeRun 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 | 4,000+ 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 CRM PipeRun in CrewAI
The CRM PipeRun 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 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
CRM PipeRun for CrewAI
Every tool call from CrewAI to the CRM PipeRun MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see my upcoming tasks and appointments?
Yes! Use the list_activities tool to retrieve all scheduled tasks and appointments. You can filter by status or owner to see exactly what's on your plate.
How do I attach a document to a specific deal?
You can use the upload_file tool. Just provide the deal_id, the file name, and the base64 encoded content of the document to attach it directly to the CRM record.
Is it possible to update the status of an existing activity?
Absolutely. Use the update_activity tool with the activity id and the new status code (e.g., 2 for 'Done') to keep your pipeline up to date.
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.
Explore More MCP Servers
View all →
Mitto
27 toolsAutomate SMS messaging and 2FA verification via Mitto — send single or bulk messages, verify OTPs, and lookup phone numbers directly from your AI agent.

Knackly
8 toolsGenerate legal and business documents from smart templates with conditional logic that adapts content to every unique situation.

Robin
10 toolsConnect your AI assistant to Robin to seamlessly manage office locations, book meeting rooms, reserve hot desks, and monitor workplace availability directly from chat.

Workast
12 toolsManage projects, tasks, and team collaboration with AI directly in your workflow.
