An astronaut overseeing a futuristic data hub

Connect Jd Cloud Infrastructure to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage your entire cloud stack through natural language.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 11 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 11 available through JD Cloud.

  1. 01

    Describe cloud disk

    Use this to get specific, granular details about a single cloud disk.

  2. 02

    Describe vm instance

    This capability provides a deep dive into the configuration and status of a specific VM.

  3. 03

    List cloud disks

    This capability lists every cloud disk volume currently active in your specified region.

  4. 04

    List vm instances

    This capability shows all virtual machine instances within your JD Cloud region.

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 11 available through JD Cloud.

  1. 05

    Reboot vm instance

    This capability performs a reboot on a specified VM instance.

  2. 06

    Start vm instance

    This capability powers on a VM instance that is currently stopped.

  3. 07

    Stop vm instance

    Use this to shut down a running VM instance.

  4. 08

    List elastic ips

    This capability retrieves a list of all Elastic IP addresses in your region.

Capability set03 / 03

09-11

3 capabilities in this set.

Part of 11 available through JD Cloud.

  1. 09

    List oss buckets

    This capability returns a list of all your Object Storage Service buckets.

  2. 10

    Describe metric data

    This capability pulls time-series monitoring metrics for any cloud resource you specify.

  3. 11

    List rds instances

    This capability lists all RDS database instances in your region, including engine versions.

Real work

What teams actually run

01

Rapid Incident Response

An SRE can ask the AI to reboot a specific VM instance immediately after seeing a spike in error rates.

02

Resource Auditing

A DevOps engineer can quickly list all Elastic IPs to check for unused allocations.

03

Performance Troubleshooting

You can ask your agent to pull CPU and disk metrics to diagnose a slow database instance.

04

Inventory Management

Use the AI to get a quick count of all active VM instances and storage buckets in a region.

Automate a task

Put JD Cloud to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

JD Cloud works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put JD Cloud to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

880ms average. Fast in production.

JD Cloud is checked daily against the live service.

Daily averagePeak 1140ms
Oct 3Today
Fastest day
639ms
Slowest day
1140ms
14-day trend
Stable-1%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 11 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of JD Cloud, so you can see the experience inside your AI.

It does not authenticate your account with JD Cloud. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

JD Cloud Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_XVyDpjLKMV2jNPAcRKkik1f5ahKvTUfXc2RxgNF0/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — JD Cloud capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "jd-cloud-infrastructure-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_XVyDpjLKMV2jNPAcRKkik1f5ahKvTUfXc2RxgNF0/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up JD Cloud in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work JD Cloud owners hand off.

This MCP is built for technical teams managing large scale JD Cloud deployments.

  • 01

    DevOps Engineers

    They use the AI to manage infrastructure without switching to the JD Cloud console.

  • 02

    SRE Teams

    They hand off metric querying and instance restarts to their AI agents.

  • 03

    Supply Chain Architects

    They use the AI to oversee the cloud backbone of logistics networks.

FAQ

Questions JD Cloud owners ask.

  • 01

    How does this MCP handle my JD Cloud credentials?

    The MCP engine constructs the JDCLOUD2-HMAC-SHA256 signature locally for every request. Your secret keys are used to sign requests without exposing them to the cloud provider in an unencrypted way.

  • 02

    Which AI clients can I use with this MCP?

    You can use any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 03

    Can I monitor performance metrics through the AI?

    Yes, you can use the describe_metric_data capability to pull time-series CPU, network, and disk metrics for your resources.

  • 04

    Does this MCP support database management?

    Yes, it includes capabilities to list RDS instances, check their engine versions, and verify connection status.

  • 05

    What happens if I want to restart a VM?

    You can simply tell your AI client to reboot the specific VM instance, and it will use the reboot_vm_instance capability to do it.

  • 06

    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.

Connect JD Cloud to Claude, Cursor, ChatGPT & more