Bring Procurement
to CrewAI
Learn how to connect YoneTeam to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the YoneTeam MCP Server?
Connect your YoneTeam (Satin Alma) account to any AI agent and streamline your entire procurement and supply chain process through natural conversation.
What you can do
- Demand Management — List and create internal purchasing demands to initiate the procurement cycle.
- Offer Comparison — Query and inspect supplier offers and quotes to make informed buying decisions.
- Order Tracking — Manage the lifecycle of purchase orders from issuance to final delivery.
- Supplier Directory — List approved suppliers and browse your materials catalog to identify sourcing options.
- Delivery Logistics — Monitor scheduled deliveries and incoming shipments to keep your operations running smoothly.
How it works
1. Subscribe to this server
2. Enter your YoneTeam API Key
3. Start managing your procurement from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Procurement Officers — quickly check the status of pending demands and compare supplier quotes via AI.
- Supply Chain Managers — monitor delivery schedules and verify material availability in real-time.
- Operations Leads — automate the creation of purchasing requests and track order progress without leaving the workspace.
Built-in capabilities (10)
Create a new purchasing demand
Get account information
Get details of a specific offer
Get details of a specific purchase order
List scheduled deliveries
List purchasing demands
List material catalog
List supplier offers
List purchase orders
List approved suppliers
Why CrewAI?
When paired with CrewAI, YoneTeam becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call YoneTeam 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
YoneTeam in CrewAI
YoneTeam and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect YoneTeam 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 YoneTeam in CrewAI
The YoneTeam 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 10 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
YoneTeam for CrewAI
Every tool call from CrewAI to the YoneTeam 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 the pricing details of a specific supplier offer?
Yes, use the get_offer_details tool with the appropriate Offer ID to retrieve full metadata and pricing information from the quote.
How do I check when a purchase order is scheduled to arrive?
You can use the list_deliveries query to see a schedule of all incoming material shipments and their estimated arrival dates.
Is it possible to list all materials available in our catalog?
Absolutely. Run the list_materials_catalog query to retrieve a complete list of items and materials currently registered in the purchasing system.
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.