Bring Experience Data
to CrewAI
Learn how to connect Pitchly to CrewAI 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 Pitchly MCP Server?
Connect your Pitchly account to any AI agent and take full control of your organizational experience and content orchestration through natural conversation. Pitchly is the data management platform of choice for professional services firms, and this integration allows you to retrieve workspace metadata, manage custom data tables, and update critical records (deals, bios, tombstones) directly from your chat interface.
What you can do
- Workspace & Table Orchestration — List all managed workspaces and retrieve detailed table structures programmatically to ensure your data foundation is always synchronized.
- Record Lifecycle Management — Query, create, and update records across custom tables with detailed profile metadata directly from the AI interface to maintain high-fidelity business intelligence.
- Content Discovery Intelligence — Search through complex data sets for specific deals, professional bios, or tombstone data via natural language to drive better research efficiency.
- Data Ingestion Control — Automate the creation of new records and manage organizational metadata using simple AI commands.
- Operational Monitoring — Track system responses and manage workspace health to ensure your experience management is always optimized.
How it works
1. Subscribe to this server
2. Enter your Pitchly API Key (Bearer Token) from your developer settings
3. Start managing your professional experience data from Claude, Cursor, or any MCP-compatible client
No more manual spreadsheet updates or searching through disparate databases. Your AI acts as a dedicated experience manager or data coordinator.
Who is this for?
- Professional Services Firms — quickly retrieve deal summaries and monitor team experience without switching apps.
- Marketing & BD Teams — automate the retrieval of tombstone data and track professional bios via natural conversation.
- Knowledge Managers — streamline the retrieval of organizational metadata and monitor data health directly within the chat.
Built-in capabilities (11)
Add a new record to a table
Delete a record from a table
Get details of a specific record
Get details of a specific table
Get details of a specific workspace
List all fields in a table
List records in a Pitchly table
List tables in a workspace
List all Pitchly workspaces
Search records within a table
Update an existing record
Why CrewAI?
When paired with CrewAI, Pitchly becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Pitchly 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
Pitchly in CrewAI
Pitchly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Pitchly 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 | 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 Pitchly in CrewAI
The Pitchly 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
Pitchly for CrewAI
Every tool call from CrewAI to the Pitchly 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 a specific deal record by its ID?
Yes! Use the get_record tool with the Table ID and Record ID. Your agent will respond with the complete metadata for the entry, including all custom field values in seconds.
How do I find my Pitchly API Key?
Log in to your Pitchly account, navigate to Settings or your Developer Dashboard, and you will find your unique secret API key there. You may need organization admin privileges to see it.
Does this work with custom tables?
Absolutely. This integration dynamically lists all tables available in your workspaces, allowing the AI to interact with any custom schema you've created for deals, bios, or projects.
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.