How do I get Cin7 Core API credentials?

Log in to Cin7 Core, navigate to **Settings > Integration > API**, and click the '+' button to create a new API application. You will be provided with an Account ID and an Application Key.

Is the stock data across all locations included?

Yes, you can check real-time stock availability across all your warehouses using the get_all_stock_availability tool.

Can the agent check order status?

Absolutely. You can list sales and purchase orders or retrieve full details for a specific order ID to check its current status and fulfillment progress.

Cin7 Core MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Cin7 Core
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Cin7 Core through Vinkius, pass the Edge URL in the `mcps` parameter and every Cin7 Core tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Cin7 Core Specialist",
    goal="Help users interact with Cin7 Core effectively",
    backstory=(
        "You are an expert at leveraging Cin7 Core tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Cin7 Core "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Cin7 Core MCP Server

Integrate Cin7 Core (formerly DEAR Systems), the advanced cloud-based inventory management platform, directly into your AI workflow. Manage your product catalog, monitor real-time stock levels, track sales and purchase orders, and research customer and supplier data using natural language.

When paired with CrewAI, Cin7 Core becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Cin7 Core tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Inventory Intelligence — List and retrieve detailed information for products and check real-time stock availability across warehouses.
Order Management — Monitor sales and purchase orders, track their status, and access full fulfillment details.
CRM & Supplier Research — Quickly access customer and supplier profiles and their historical interactions.
Multi-warehouse Oversight — Track inventory locations and stock movement efficiently via chat.

The Cin7 Core MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Cin7 Core to CrewAI via MCP

Follow these steps to integrate the Cin7 Core MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Cin7 Core

Why Use CrewAI with the Cin7 Core MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Cin7 Core through the Model Context Protocol.

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 `mcps` parameter 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

Cin7 Core + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Cin7 Core MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Cin7 Core for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Cin7 Core, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Cin7 Core tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Cin7 Core against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Cin7 Core MCP Tools for CrewAI (10)

These 10 tools become available when you connect Cin7 Core to CrewAI via MCP:

get_all_stock_availability

Returns real-time availability data including on-hand, allocated, and available-to-sell quantities across all configured warehouse locations. Retrieve current stock availability across all warehouses

get_product_details

Resolves detailed attributes such as dimensions, weight, supplier info, and tax rules for the given product GUID. Get detailed information for a specific product by ID

get_sale_order_details

Resolves individual line items, shipping addresses, invoice details, and the current fulfillment progress. Get full details for a specific sales order

get_sku_stock_status

Provides a detailed breakdown of quantities across all physical locations and virtual bins. Get stock levels for a specific product SKU

list_crm_customers

Returns customer metadata including contact names, company details, and credit limits. List all customers registered in the system

list_crm_suppliers

Returns vendor profiles including primary contact info, default currency, and payment terms. List all suppliers and vendors

list_inventory_products

Returns a list of products with metadata including SKU, name, category, and base price. List all products in your Cin7 Core (DEAR) catalog

list_purchase_orders

Returns a list of purchase orders including supplier details, order date, and inbound status (e.g., ordered, received). List all purchase orders and inbound shipments

list_sales_orders

Returns order metadata including customer ID, total value, and current status (e.g., drafted, authorized, packed, shipped). List all sales orders and their current fulfillment status

search_products_by_sku

Returns stock and identification data for products matching the provided SKU identifier. Search for a product using its SKU

Example Prompts for Cin7 Core in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Cin7 Core immediately.

"What is the stock level for product SKU 'CH-1001'?"

"List all sales orders that are currently 'Awaiting Fulfillment'."

"Show me the contact details for supplier 'Furniture Pros'."

Troubleshooting Cin7 Core MCP Server with CrewAI

Common issues when connecting Cin7 Core to CrewAI through the Vinkius, and how to resolve them.

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.

Cin7 Core + CrewAI FAQ

Common questions about integrating Cin7 Core MCP Server with CrewAI.

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.