Kimi Code

How to give Kimi Code access to Triathlon Pace Planner

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

Ask AI about this guide

Triathlon Pace Planner Connector

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

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

Connecting Triathlon Pace Planner 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 Triathlon Pace Planner with your link in the url field. The link above is the URL.
  3. 3Run /mcp to confirm the status, then ask something real. Triathlon Pace Planner is now part of Kimi Code.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "triathlon-pace-planner-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_NPsvf322ML7HOQ9lfUs5RNE4eaRdJBCmAAHijo0G/mcp"
    }
  }
}

Kimi Code + Triathlon Pace Planner

One chat. Your Triathlon Pace Planner, 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 Triathlon Pace Planner Connector. Once yours is connected, they work in your sessions.

The full capability set, the prompts and the observed latency live on the Triathlon Pace Planner Connector page.

Mission Control

See everything your Kimi Code agents do in Triathlon Pace Planner.

When Kimi Code runs a tool in Triathlon Pace Planner, 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 Triathlon Pace Planner is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your Triathlon Pace Planner workflows.

What sets us apart

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

Connecting Triathlon Pace Planner to your AI is step one. But an open line between your agents and Triathlon Pace Planner 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 Triathlon Pace Planner is recorded and signed, so any change to the history becomes detectable.

02

Automatic Key Rotation

We rotate security keys every 24 hours. Your Triathlon Pace Planner 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 Triathlon Pace Planner actions never surprise you.

04

Isolated Sandbox

Every execution through Triathlon Pace Planner 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 Triathlon Pace Planner 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 Triathlon Pace Planner.

08

Credential Validation

We test your Triathlon Pace Planner 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 Triathlon Pace Planner connection runs on. Read how our infrastructure protects everything your Kimi Code agents do, end to end.

Inside Vinkius

Get Triathlon Pace Planner ready for your AI. It's easy.

You choose Triathlon Pace Planner from the Vinkius Catalog and get one connection link. That's it.

  1. You choose Triathlon Pace Planner

    You find Triathlon Pace Planner in the Catalog and install the Connector with one click.

    Triathlon Pace Planner

    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_NPsvf322ML7HOQ9lfUs5RNE4eaRdJBCmAAHijo0G/mcp

    Connection Token

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

Set it up once. Use Triathlon Pace Planner 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 Triathlon Pace Planner to Kimi Code, can I use the same connection in Claude or ChatGPT later?

    Yes, and that's the point: the connection is yours, not Kimi Code'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 Triathlon Pace Planner is already there.

  • 03

    Do I need to hand my Triathlon Pace Planner password to Kimi Code?

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

  • 04

    What can I actually ask Kimi Code to do with Triathlon Pace Planner?

    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

    Kimi Code 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 Triathlon Pace Planner? The Connector page answers them. See everything the Triathlon Pace Planner Connector can do

About the Connector

What Triathlon Pace Planner adds to your AI.

Once you connect it, your AI gains 4 capabilities: the exact actions it can take in Triathlon Pace Planner 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 Triathlon Pace Planner Connector can do