Bring Channel Sales
to CrewAI
Learn how to connect PartnerPortal.io 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 PartnerPortal.io MCP Server?
Connect your PartnerPortal.io account to any AI agent and take full control of your channel sales orchestration and partner relationship management through natural conversation. PartnerPortal.io provides a comprehensive platform for scaling partner ecosystems, and this integration allows you to retrieve lead metadata, monitor active deals, and manage partner accounts directly from your chat interface.
What you can do
- Lead & Opportunity Orchestration — List, create, and update leads programmatically across your partner network to ensure your sales pipeline is always synchronized.
- Partner & Account Intelligence — Access and monitor partner profiles and account-level metadata directly from the AI interface to maintain high-fidelity relationships.
- Deal Lifecycle Control — Access and monitor deal statuses via natural language to track channel revenue growth and partner performance.
- Schema & Metadata Oversight — Retrieve object schemas and list account roles using simple AI commands to ensure your data mapping is always optimized.
- Operational Monitoring — Track system responses and manage bulk creation jobs to ensure your partner operations are always high-performing.
How it works
1. Subscribe to this server
2. Enter your PartnerPortal.io API Token (Bearer Token) from your dashboard
3. Start managing your partner program from Claude, Cursor, or any MCP-compatible client
No more manual status checking in the portal. Your AI acts as a dedicated channel manager or partnership coordinator.
Who is this for?
- Channel Managers — quickly retrieve partner performance summaries and monitor lead volume without switching apps.
- Partnership Teams — automate the creation of new leads and track deal progress via natural conversation.
- Operations Leads — streamline the retrieval of account metadata and monitor organizational partnership health directly within the chat.
Built-in capabilities (11)
Verify API connectivity and account status
Create a new lead
Get details for a specific account
Get details for a specific deal
Get details for a specific lead
Get details for a specific partner
List accounts in PartnerPortal.io
List deals in PartnerPortal.io
io. List leads in PartnerPortal.io
List partners in PartnerPortal.io
Update an existing lead
Why CrewAI?
When paired with CrewAI, PartnerPortal.io becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call PartnerPortal.io 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
PartnerPortal.io in CrewAI
PartnerPortal.io and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect PartnerPortal.io 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 PartnerPortal.io in CrewAI
The PartnerPortal.io 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
PartnerPortal.io for CrewAI
Every tool call from CrewAI to the PartnerPortal.io 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 for a specific lead by its ID?
Yes! Use the get_lead tool with the Company ID and Lead ID. Your agent will respond with complete metadata, including lead status, source, and associated deal info in seconds.
How do I find my PartnerPortal.io API Token?
Log in to your PartnerPortal.io account, navigate to Settings > API, and you will find or generate your unique secret token there. Ensure you have the required plan level for API access.
What is the Company ID?
The Company ID is a unique identifier for your organization profile within PartnerPortal.io. You can find it in your portal settings or URL after logging in.
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.