Cursor

How to give Cursor access to Bot9

Set up in seconds, once. From then on, Cursor gets things done for you: edit one config file, and Bot9 is live in Cursor.

Ask AI about this guide

Bot9 Connector

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

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

Connecting Bot9 to Cursor

About a minute, in Cursor

  1. 1Open Customize in the Cursor sidebar (or create .cursor/mcp.json in your project).
  2. 2Add an MCP server named Bot9 with the url field set to your link. The link above is the URL.
  3. 3Save, enable the server, and ask something real. Bot9 is now part of Cursor.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "bot9-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_xykFN1NHKp6fhi8a6feYwqUybPGEA4E4VDUoP8es/mcp"
    }
  }
}

Cursor + Bot9

One chat. Your Bot9, live inside Cursor.

Real prompts, answered with live data. This is the kind of session you will have in Cursor once the server 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 Bot9 Connector. Once yours is connected, they work in your sessions.

The full capability set, the prompts and the observed latency live on the Bot9 Connector page.

Mission Control

See everything your Cursor agents do in Bot9.

When Cursor runs a tool in Bot9, 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 Cursor agents make through Bot9 is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your Bot9 workflows.

What sets us apart

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

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

02

Automatic Key Rotation

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

04

Isolated Sandbox

Every execution through Bot9 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 Bot9 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 Cursor sessions responsive.

07

Malicious File Protection

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

08

Credential Validation

We test your Bot9 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 Bot9 connection runs on. Read how our infrastructure protects everything your Cursor agents do, end to end.

Inside Vinkius

Get Bot9 ready for your AI. It's easy.

You choose Bot9 from the Vinkius Catalog, sign in to your Bot9 account, and get one connection link. That's it.

  1. You choose Bot9

    You find Bot9 in the Catalog and install the Connector with one click.

    Bot9

    Active

    Enable Connector
    Activating…

  2. You sign in

    You connect your Bot9 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}}

    RequiredEncrypted
    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.

  3. You add the link in Cursor

    Vinkius gives you one connection link. In Cursor, you add an MCP server named Bot9 with the link in the url field, and the connection is ready.

    Token generated successfully

    MCP Connection URL

    https://edge.vinkius.com/vk_preview_xykFN1NHKp6fhi8a6feYwqUybPGEA4E4VDUoP8es/mcp

    Connection Token

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

Set it up once. Use Bot9 with the AI you already use.

FAQ

Cursor access questions.

  • 01

    Where does this work?

    In Cursor itself: the Customize page manages servers, and the config lives in .cursor/mcp.json (project) or ~/.cursor/mcp.json (global), with the url field for remote servers.

  • 02

    If I connect Bot9 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 Bot9 is already there.

  • 03

    Do I need to hand my Bot9 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 Bot9?

    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?

    Make sure the server is enabled on the Customize page and the url was pasted exactly as copied, then confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.

  • 06

    Can I remove the access later?

    Remove the server from your mcp.json (or toggle it off on the Customize page) and it's out of Cursor. Your Vinkius account keeps the connection and its history either way, ready for the next AI.

  • More questions about Bot9? The Connector page answers them. See everything the Bot9 Connector can do

About the Connector

What Bot9 adds to your AI.

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