Is the JDCLOUD2-HMAC-SHA256 signing handled automatically?

Yes. The MCP engine locally derives signing keys through HMAC chains (date → region → service → jdcloud2_request), constructs canonical requests, and injects the Authorization header transparently. Your AI never handles raw crypto.

JD Cloud Infrastructure MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: JD Cloud Infrastructure
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to JD Cloud Infrastructure through Vinkius, pass the Edge URL in the `mcps` parameter and every JD Cloud Infrastructure 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="JD Cloud Infrastructure Specialist",
    goal="Help users interact with JD Cloud Infrastructure effectively",
    backstory=(
        "You are an expert at leveraging JD Cloud Infrastructure 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 JD Cloud Infrastructure "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 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 JD Cloud Infrastructure MCP Server

Connect your AI agents directly to JD Cloud (京东云), the enterprise cloud infrastructure backing one of the world's largest e-commerce and supply chain platforms. This MCP provides 11 power tools spanning the full infrastructure lifecycle.

When paired with CrewAI, JD Cloud Infrastructure becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call JD Cloud Infrastructure 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

VM Lifecycle Management — List, inspect, start, stop, and reboot virtual machines through natural language
Storage Operations — Enumerate and inspect cloud disks and Object Storage buckets
Network Oversight — Query Elastic IP allocations and their association status
Database Administration — List RDS instances with engine versions and connection status
Performance Monitoring — Pull time-series CPU, network, and disk metrics for any resource

The JD Cloud Infrastructure MCP Server exposes 11 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 JD Cloud Infrastructure to CrewAI via MCP

Follow these steps to integrate the JD Cloud Infrastructure 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 11 tools from JD Cloud Infrastructure

Why Use CrewAI with the JD Cloud Infrastructure MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with JD Cloud Infrastructure 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

JD Cloud Infrastructure + CrewAI Use Cases

Practical scenarios where CrewAI combined with the JD Cloud Infrastructure MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries JD Cloud Infrastructure 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 JD Cloud Infrastructure, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain JD Cloud Infrastructure 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 JD Cloud Infrastructure against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

JD Cloud Infrastructure MCP Tools for CrewAI (11)

These 11 tools become available when you connect JD Cloud Infrastructure to CrewAI via MCP:

describe_cloud_disk

Get detailed information about a specific cloud disk

describe_metric_data

Query monitoring metric data for a cloud resource

describe_vm_instance

Get detailed information about a specific VM instance

list_cloud_disks

List all cloud disk volumes in your region

list_elastic_ips

List all Elastic IP addresses in your region

list_oss_buckets

List all Object Storage Service buckets

list_rds_instances

List all RDS database instances in your region

list_vm_instances

List all virtual machine instances in your JD Cloud region

reboot_vm_instance

Reboot a VM instance

start_vm_instance

Start a stopped VM instance

stop_vm_instance

Stop a running VM instance

Example Prompts for JD Cloud Infrastructure in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with JD Cloud Infrastructure immediately.

"List all my running virtual machines on JD Cloud."

"Show me the CPU usage for instance i-abc123 over the last hour."

Troubleshooting JD Cloud Infrastructure MCP Server with CrewAI

Common issues when connecting JD Cloud Infrastructure 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.

JD Cloud Infrastructure + CrewAI FAQ

Common questions about integrating JD Cloud Infrastructure 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.