VS Code

How to give VS Code access to Maker-Space Access Planner

Set up in seconds, once. From then on, VS Code gets things done for you: add one server entry, and Maker-Space Access Planner is live in Copilot Chat.

Ask AI about this guide

Maker-Space Access Planner Connector

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

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

Connecting Maker-Space Access Planner 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 Maker-Space Access Planner with type http and your link as the url. The link above is the URL.
  3. 3Save and ask something real in Copilot Chat. Maker-Space Access Planner is now part of VS Code.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "maker-space-access-planner-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_msVTrqCN4rV0NpYGk0REqIB1L6kJ9zQ4xD6FEH2K/mcp"
    }
  }
}

VS Code + Maker-Space Access Planner

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

The full capability set, the prompts and the observed latency live on the Maker-Space Access Planner Connector page.

Mission Control

See everything your VS Code agents do in Maker-Space Access Planner.

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

What sets us apart

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

Connecting Maker-Space Access Planner to your AI is step one. But an open line between your agents and Maker-Space Access 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 Maker-Space Access 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 Maker-Space Access 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 Maker-Space Access Planner actions never surprise you.

04

Isolated Sandbox

Every execution through Maker-Space Access 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 Maker-Space Access 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 VS Code sessions responsive.

07

Malicious File Protection

We detect compressed files designed to exhaust system resources and block them before they ever reach Maker-Space Access Planner.

08

Credential Validation

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

Inside Vinkius

Get Maker-Space Access Planner ready for your AI. It's easy.

You choose Maker-Space Access Planner from the Vinkius Catalog and get one connection link. That's it.

  1. You choose Maker-Space Access Planner

    You find Maker-Space Access Planner in the Catalog and install the Connector with one click.

    Maker-Space Access Planner

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

    Connection Token

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

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

    Yes, and that's the point: the connection is yours, not VS 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 Maker-Space Access Planner is already there.

  • 03

    Do I need to hand my Maker-Space Access Planner password to VS Code?

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

  • 04

    What can I actually ask VS Code to do with Maker-Space Access 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

    VS Code 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 Maker-Space Access Planner? The Connector page answers them. See everything the Maker-Space Access Planner Connector can do

About the Connector

What Maker-Space Access Planner adds to your AI.

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