Kimi Code

How to give Kimi Code access to PubMed / NCBI

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

Ask AI about this guide

PubMed / NCBI Connector

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

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

Connecting PubMed / NCBI to Kimi Code

About a minute, in the TUI

  1. 1Run /mcp-config in the Kimi Code TUI to add a server interactively (or edit mcp.json directly).
  2. 2Add a server named PubMed / NCBI with your link in the url field. The link above is the URL.
  3. 3Run /mcp to confirm the status, then ask something real. PubMed / NCBI is now part of Kimi Code.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "stanford-pubmed-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_Er4T2DNOmXIPgLSBD4Sg49CsDjikKCAGM5l5oUWB/mcp"
    }
  }
}

Kimi Code + PubMed / NCBI

One chat. Your PubMed / NCBI, 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.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

These prompts ship with the PubMed / NCBI Connector. Once yours is connected, they work in your sessions.

The full capability set, the prompts and the observed latency live on the PubMed / NCBI Connector page.

Mission Control

See everything your Kimi Code agents do in PubMed / NCBI.

When Kimi Code runs a tool in PubMed / NCBI, 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
0
Total in this period
Avg Latency
0
API 88ms · Overhead 54ms
Vinkius Reliability
0
Agent 280 · Upstream 47 · Vinkius 15
Tokens
0
AI tokens processed
DLP Protected
0
Sensitive data redacted
Cost Saved
0
FinOps truncations applied

AI Agents Activities

last 30 days
30d agotoday

Request Volume & Latency

requests latency

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

What sets us apart

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

Connecting PubMed / NCBI to your AI is step one. But an open line between your agents and PubMed / NCBI 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.

01

Tamper Proof Activity Log

Every request your agents make in PubMed / NCBI is recorded and signed, so any change to the history becomes detectable.

02

Automatic Key Rotation

We rotate security keys every 24 hours. Your PubMed / NCBI connection stays protected without any manual work.

03

Spending Protection

We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your PubMed / NCBI actions never surprise you.

04

Isolated Sandbox

Every execution through PubMed / NCBI runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.

05

Security Event Streaming

Security events flow to Splunk, Datadog or your own webhook, so PubMed / NCBI activity lands in the tools you already rely on.

06

Instant Resume

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

07

Malicious File Protection

We detect compressed files designed to exhaust system resources and block them before they ever reach PubMed / NCBI.

08

Credential Validation

We test your PubMed / NCBI credentials before saving them. Invalid credentials are rejected instead of being stored.

09

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 PubMed / NCBI connection runs on. Read how our infrastructure protects everything your Kimi Code agents do, end to end.

Inside Vinkius

Get PubMed / NCBI ready for your AI. It's easy.

You choose PubMed / NCBI from the Vinkius Catalog and get one connection link. That's it.

  1. You choose PubMed / NCBI

    You find PubMed / NCBI in the Catalog and install the Connector with one click.

    PubMed / NCBI

    Active

    Enable Connector
    Activating…

  2. 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_Er4T2DNOmXIPgLSBD4Sg49CsDjikKCAGM5l5oUWB/mcp

    Connection Token

    vk_live_••••••••
    Go to Dashboard

Set it up once. Use PubMed / NCBI 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 PubMed / NCBI 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 PubMed / NCBI is already there.

  • 03

    Do I need to hand my PubMed / NCBI 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 PubMed / NCBI?

    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 PubMed / NCBI? The Connector page answers them. See everything the PubMed / NCBI Connector can do

About the Connector

What PubMed / NCBI adds to your AI.

Once you connect it, your AI gains 16 capabilities: the exact actions it can take in PubMed / NCBI 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 PubMed / NCBI Connector can do