How to Use the Gridscale (IaaS & PaaS Cloud Hosting API) MCP in Cursor

Q: Can I use Cursor to link IP addresses to my Gridscale (IaaS & PaaS Cloud Hosting API) servers?

Absolutely. Your Cursor agent uses listips to find unassigned addresses and runs linkiptoserver to map them to your Gridscale nodes. You can configure your entire Gridscale networking stack without leaving your Cursor code editor.

Q: Does this MCP Server let me manage PaaS services inside Cursor?

Yes, this MCP Server exposes the listpaas tool so Cursor can query databases. Cursor uses this to inspect your active Gridscale database and caching clusters, helping you write accurate connection strings for your application.

Q: How do I select the right server template when coding in Cursor?

Your MCP Server runs listtemplates to get a list of active Gridscale OS images. It then feeds those exact template IDs directly into your createserver configuration scripts in Cursor so you never deploy an unsupported OS.

Code and provision your Gridscale cloud infrastructure directly inside Cursor using real-time server telemetry.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Gridscale (IaaS & PaaS Cloud Hosting API) MCP to Cursor

Create your Vinkius account to connect Gridscale (IaaS & PaaS Cloud Hosting API) to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Gridscale (IaaS & PaaS Cloud Hosting API) with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build server setup scripts in Cursor with real API data

Stop writing code in Cursor against fake Gridscale API responses. Cursor uses this MCP Server to run `list_servers` and `list_networks` to pull your actual Gridscale environment into your editor, letting Composer generate code that matches your live setup. When you need to spin up a new node, Cursor calls `create_server` using your real Gridscale account templates. You write Gridscale configuration files in Cursor that work on the first run because they use your actual infrastructure parameters.

Diagnose performance issues directly from your editor

If your application is throwing errors, ask Cursor to check the Gridscale server state. The editor runs `get_server_metrics` to grab real-time performance data and displays your Gridscale telemetry alongside your codebase. Your Cursor agent analyzes these metrics to pinpoint resource bottlenecks on your Gridscale nodes. You don't have to leave Cursor to check if a CPU spike or disk I/O limit is causing your Gridscale database queries to hang.

Control server power states during local development

You can manage your remote Gridscale development nodes without leaving your active Cursor file. Cursor runs `get_server_power` to check if a machine is active, then executes `set_server_power` or `shutdown_server` on your Gridscale nodes. This lets you pause expensive Gridscale testing nodes when you finish a coding session in Cursor. Your agent keeps your Gridscale cloud spend low by ensuring idle servers are shut down directly from the Cursor terminal panel.

Setup guide

Set up Gridscale (IaaS & PaaS Cloud Hosting API) MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Gridscale (IaaS & PaaS Cloud Hosting API) MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Gridscale (IaaS & PaaS Cloud Hosting API) transactions." If the MCP tools are loaded correctly, Cursor will call the Gridscale (IaaS & PaaS Cloud Hosting API) tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "gridscale-iaas-paas-cloud-hosting-api-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Gridscale. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Gridscale (IaaS & PaaS Cloud Hosting API) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Gridscale (IaaS & PaaS Cloud Hosting API) MCP in Cursor

Create an mcp.json file in your project's .cursor directory and add the Gridscale MCP Server configuration. Once enabled, your Cursor agent can run tools like `list_servers` to pull real-time Gridscale cloud data straight into your active workspace.

Absolutely. Your Cursor agent uses `list_ips` to find unassigned addresses and runs `link_ip_to_server` to map them to your Gridscale nodes. You can configure your entire Gridscale networking stack without leaving your Cursor code editor.

Yes, this MCP Server exposes the `list_paas` tool so Cursor can query databases. Cursor uses this to inspect your active Gridscale database and caching clusters, helping you write accurate connection strings for your application.

Your MCP Server runs `list_templates` to get a list of active Gridscale OS images. It then feeds those exact template IDs directly into your `create_server` configuration scripts in Cursor so you never deploy an unsupported OS.

Cursor accesses your Gridscale API tokens directly from your local environment variables. The connection goes through a secure V8 isolate sandbox that wipes all memory upon completion, keeping your Gridscale server configurations safe.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript