Does this work inside the Kimi Code TUI?

Yes. Run /mcp to check the connection status of every server, and /mcp-config login to complete browser-based authorization for remote servers.

If I connect JD Cloud / 京东云 to Gemini, can I use the same connection in Claude or ChatGPT later?

Yes, and that's the point: the connection is yours, not Gemini's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and JD Cloud / 京东云 is already there.

Do I need to hand my JD Cloud / 京东云 password to Gemini?

Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Gemini only ever sees the link, and you can remove it whenever you want.

What can I actually ask Gemini to do with JD Cloud / 京东云?

Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.

Gemini doesn't show the Connector. What do I check?

Run /mcp to check the connection status, confirm the url in mcp.json matches your link exactly, and confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.

Can I remove the access later?

Remove the entry from mcp.json (or delete it in /mcp-config) and it's out of your sessions. Your Vinkius account keeps the connection and its history either way, ready for the next AI.

How to give Kimi Code access to JD Cloud / 京东云

Set up in seconds, once. From then on, Kimi Code gets things done for you: add one server entry, and JD Cloud / 京东云 is live in your terminal.

Ask AI about this guide

JD Cloud / 京东云 Connector

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

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

Connecting JD Cloud / 京东云 to Kimi Code

About a minute, in the TUI

1Run /mcp-config in the Kimi Code TUI to add a server interactively (or edit mcp.json directly).
2Add a server named JD Cloud / 京东云 with your link in the url field. The link above is the URL.
3Run /mcp to confirm the status, then ask something real. JD Cloud / 京东云 is now part of Kimi Code.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "jd-cloud-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_zMsgAjxvJjrelUl5HM2CU1SLPPaXwxfXYoqu6vZr/mcp"
    }
  }
}

Kimi Code + JD Cloud / 京东云

One chat. Your JD Cloud / 京东云, live inside Kimi Code.

Real prompts, answered with live data. This is the kind of session you will have in Kimi Code once the link is in.

Waiting for input…

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

These prompts ship with the JD Cloud / 京东云 Connector. Once yours is connected, they work in your sessions.

The full capability set, the prompts and the observed latency live on the JD Cloud / 京东云 Connector page.

Mission Control

See everything your Kimi Code agents do in JD Cloud / 京东云.

When Kimi Code runs a tool in JD Cloud / 京东云, it happens in your editor: you see the result, but not the request itself, what data it carried, or whether a rule was broken.

Now every move lands on your screen.

Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.

AI Briefing

Upgrade to unlock

Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.

Requests

Total in this period

Avg Latency

API 88ms · Overhead 54ms

Vinkius Reliability

Agent 280 · Upstream 47 · Vinkius 15

Tokens

AI tokens processed

DLP Protected

Sensitive data redacted

Cost Saved

FinOps truncations applied

AI Agents Activities

last 30 days

30d agotoday

Request Volume & Latency

requests latency

Every request your Kimi Code agents make through JD Cloud / 京东云 is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your JD Cloud / 京东云 workflows.

What sets us apart

It's not just the Connector that stays safe. Everything your agents do through it is.

Connecting JD Cloud / 京东云 to your AI is step one. But an open line between your agents and JD Cloud / 京东云 is only half the story: without protection, every action they take runs unguarded.

That's why protection doesn't stop at the door.

Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.

Tamper Proof Activity Log

Every request your agents make in JD Cloud / 京东云 is recorded and signed, so any change to the history becomes detectable.

Automatic Key Rotation

We rotate security keys every 24 hours. Your JD Cloud / 京东云 connection stays protected without any manual work.

Spending Protection

We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your JD Cloud / 京东云 actions never surprise you.

Isolated Sandbox

Every execution through JD Cloud / 京东云 runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.

Security Event Streaming

Security events flow to Splunk, Datadog or your own webhook, so JD Cloud / 京东云 activity lands in the tools you already rely on.

Instant Resume

Idle connections resume in 3 to 5 ms while preserving their state, keeping your Kimi Code sessions responsive.

Malicious File Protection

We detect compressed files designed to exhaust system resources and block them before they ever reach JD Cloud / 京东云.

Credential Validation

We test your JD Cloud / 京东云 credentials before saving them. Invalid credentials are rejected instead of being stored.

Separate Usage Limits

Usage stays isolated per account, so activity in one connection never consumes another account's allowance.

One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.

These guarantees are not add-ons: they are the infrastructure every JD Cloud / 京东云 connection runs on. Read how our infrastructure protects everything your Kimi Code agents do, end to end.

Inside Vinkius

Get JD Cloud / 京东云 ready for your AI. It's easy.

You choose JD Cloud / 京东云 from the Vinkius Catalog, sign in to your JD Cloud / 京东云 account, and get one connection link. That's it.

You choose JD Cloud / 京东云
You find JD Cloud / 京东云 in the Catalog and install the Connector with one click.
JD Cloud / 京东云
Active
Enable Connector
Activating…
You sign in
You connect your JD Cloud / 京东云 account and choose what you want your AI to access. Your credentials stay encrypted and separate from your AI.
Configure Credentials
Configure credentials for {{connectorName}}
JD Cloud / 京东云 sign-inRequiredEncrypted
Save & Continue
Encrypted Storage
Your credentials are encrypted at rest and in transit.
Never Shared
Your credentials are never shared with third parties.
Full Control
Revoke or update credentials at any time.
You add the link in Kimi Code
Vinkius gives you one connection link. In the Kimi Code TUI, you add a server in /mcp-config with the link in the url field, and the connection is ready.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_zMsgAjxvJjrelUl5HM2CU1SLPPaXwxfXYoqu6vZr/mcp
Connection Token
vk_live_••••••••
Go to Dashboard

Set it up once. Use JD Cloud / 京东云 with the AI you already use.

FAQ

Kimi Code access questions.

01
Does this work inside the Kimi Code TUI?
Yes. Run /mcp to check the connection status of every server, and /mcp-config login <server-name> to complete browser-based authorization for remote servers.
02
If I connect JD Cloud / 京东云 to Gemini, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not Gemini's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and JD Cloud / 京东云 is already there.
03
Do I need to hand my JD Cloud / 京东云 password to Gemini?
Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Gemini only ever sees the link, and you can remove it whenever you want.
04
What can I actually ask Gemini to do with JD Cloud / 京东云?
Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.
05
Gemini doesn't show the Connector. What do I check?
Run /mcp to check the connection status, confirm the url in mcp.json matches your link exactly, and confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.
06
Can I remove the access later?
Remove the entry from mcp.json (or delete it in /mcp-config) and it's out of your sessions. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about JD Cloud / 京东云? The Connector page answers them. See everything the JD Cloud / 京东云 Connector can do

About the Connector

What JD Cloud / 京东云 adds to your AI.

Once you connect it, your AI gains 8 capabilities: the exact actions it can take in JD Cloud / 京东云 when you ask. The Connector page lists every one of them in detail, alongside the latency we measure in production and prompts worth trying first.

See everything the JD Cloud / 京东云 Connector can do