VS Code

How to give VS Code access to Surf Wax Estimator

Set up in seconds, once. From then on, VS Code gets things done for you: add one server entry, and Surf Wax Estimator is live in Copilot Chat.

Ask AI about this guide

Surf Wax Estimator Connector

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

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

Connecting Surf Wax Estimator to VS Code

About a minute, in VS Code

  1. 1Run MCP: Add Server from the Command Palette (or create .vscode/mcp.json in your project).
  2. 2Add a server named Surf Wax Estimator with type http and your link as the url. The link above is the URL.
  3. 3Save and ask something real in Copilot Chat. Surf Wax Estimator is now part of VS Code.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "surf-wax-consumption-estimator-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_S6lodPcveFqecacwdexbR2Z2jhXaSZh2Z7NmxxoO/mcp"
    }
  }
}

VS Code + Surf Wax Estimator

One chat. Your Surf Wax Estimator, live inside VS Code.

Real prompts, answered with live data. This is the kind of session you will have in VS Code 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 Surf Wax Estimator Connector. Once yours is connected, they work in your sessions.

The full capability set, the prompts and the observed latency live on the Surf Wax Estimator Connector page.

Mission Control

See everything your VS Code agents do in Surf Wax Estimator.

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

What sets us apart

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

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

02

Automatic Key Rotation

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

04

Isolated Sandbox

Every execution through Surf Wax Estimator 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 Surf Wax Estimator 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 VS Code sessions responsive.

07

Malicious File Protection

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

08

Credential Validation

We test your Surf Wax Estimator 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 Surf Wax Estimator connection runs on. Read how our infrastructure protects everything your VS Code agents do, end to end.

Inside Vinkius

Get Surf Wax Estimator ready for your AI. It's easy.

You choose Surf Wax Estimator from the Vinkius Catalog and get one connection link. That's it.

  1. You choose Surf Wax Estimator

    You find Surf Wax Estimator in the Catalog and install the Connector with one click.

    Surf Wax Estimator

    Active

    Enable Connector
    Activating…

  2. You add the link in VS Code

    Vinkius gives you one connection link. In VS Code, you run MCP: Add Server or add an entry in .vscode/mcp.json with your link as the url, and the connection is ready.

    Token generated successfully

    MCP Connection URL

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

    Connection Token

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

Set it up once. Use Surf Wax Estimator with the AI you already use.

FAQ

VS Code access questions.

  • 01

    Which VS Code feature does this use?

    The MCP support built into VS Code: run MCP: Add Server from the Command Palette, or use .vscode/mcp.json (workspace) and the user profile config, with type http and the url field for remote servers.

  • 02

    If I connect Surf Wax Estimator 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 Surf Wax Estimator is already there.

  • 03

    Do I need to hand my Surf Wax Estimator 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 Surf Wax Estimator?

    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 appears in your MCP list 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 run MCP: Open User Configuration to edit it) 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 Surf Wax Estimator? The Connector page answers them. See everything the Surf Wax Estimator Connector can do

About the Connector

What Surf Wax Estimator adds to your AI.

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