Gridscale MCP for AI. Control servers and network resources via chat.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
Gridscale Cloud Hosting MCP. Manage your entire cloud infrastructure—servers, networking, databases, storage volumes—directly through natural language prompts in any AI agent.
Provision new compute nodes, check real-time CPU usage, and manage firewall rules without leaving your chat interface.
What AI agents can do with Gridscale (IaaS & PaaS Cloud Hosting API) Automation
Create server
Builds and provisions an entirely new cloud server instance for your account.
Get server metrics
Pulls performance data, like CPU usage or IOPS, for a specific running server.
Get server power
Checks the current power status of any given server (on, off, etc.).
Create new compute servers or change their power state (on/off) through simple commands.
Get real-time metrics, including CPU usage and storage IOPS, for specific servers to assess health.
Manage IP addresses, private networks, and firewall rules associated with your cloud resources.
Connect storage volumes or ISO images to servers when they're ready for deployment.
List and manage managed services like databases, Redis instances, and other platform components.
Ask an AI about this
Waiting for input…
What AI agents can do with Gridscale API: 17 Tools for Infrastructure Management
These tools let you perform every action on the Gridscale platform—from creating servers to checking metrics and managing network rules.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Gridscale (IaaS & PaaS Cloud Hosting API) on VinkiusCreate Server
Builds and provisions an entirely new cloud server instance for your account.
Get Server Metrics
Pulls performance data, like CPU usage or IOPS, for a specific running server.
Get Server Power
Checks the current power status of any given server (on, off, etc.).
Link Ip To Server
Attaches a specific IP address to a running or stopped cloud server.
Link Storage To Server
Connects an existing storage volume to a server, which usually requires the server...
List Deleted
Retrieves historical records of objects that have been marked for deletion.
List Firewalls
Shows a list of all existing firewall rules and configurations.
List Ips
Gives you an inventory of every IP address assigned to your account.
List Iso Images
Retrieves a list of all available operating system ISO images for deployment.
List Locations
Shows the datacenters or physical locations where you can provision new cloud...
List Networks
Lists all defined private networks within your Gridscale account.
List Paas
Provides an inventory of managed platform services like databases and Redis instances.
List Servers
Returns a full list of every server currently registered in your Gridscale account.
List Storages
Lists all available and existing storage volumes you own.
List Templates
Shows a list of pre-defined machine images or templates for quick resource...
Set Server Power
Changes the power status of a server, setting it to on or off.
Shutdown Server
Initiates a proper ACPI shutdown procedure for a specified cloud server.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Gridscale (IaaS & PaaS Cloud Hosting API), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 17 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The old way of checking cloud infrastructure state is slow.
Today, auditing your cloud setup means jumping between the main dashboard, the networking tab for IP checks, and finally the monitoring section to see CPU load. You spend time copying IDs from one pane to another and manually cross-referencing which server belongs to which network.
With this MCP, you just tell your agent, 'Audit servers in Region A.' It gathers all those disparate data points—server list, IP range, performance metrics—and hands it back to you instantly. The whole thing is one conversation.
Managing server resources with the Gridscale MCP
The ability to run a full cycle of operations—from listing all available network structures (list_networks) and selecting an IP address (list_ips), to creating a new instance (create_server)—all within your chat context is huge. You don't lose flow.
This means the difference between spending twenty minutes clicking around dashboards, and getting the result you need in seconds. It's pure operational speed.
What your AI can actually do with this
Need to make a change on your cloud setup? You don't have to log into five different dashboards or remember complex CLI syntax just to audit a few resources. This MCP connects your AI agent directly to Gridscale’s entire suite of IaaS and PaaS tools. You talk about what you need—like starting up a staging server or checking the CPU load on production nodes—and it handles the API calls, giving you immediate status reports.
It lets you manage everything from creating new virtual machines and linking storage volumes to listing available IP addresses and managing firewall rules, all through conversation. If your team uses Vinkius for its centralized catalog of MCPs, this connector makes sure cloud infrastructure management is just another task you delegate to your agent.
019e5d22-8c3a-73cb-949e-190ee4c8c772 Here's how it actually works
The bottom line is you tell your agent what infrastructure state you need, and it executes the required API calls across Gridscale’s services.
Subscribe to this MCP using your Gridscale User ID and API Token.
Connect the credentials to any compatible AI agent (like Claude or Cursor).
Use natural language prompts, like 'List all servers that are currently offline,' and receive actionable data back.
Who is this actually for?
This MCP is for platform teams who are tired of context switching. If your job involves checking server health at 2 AM or manually running resource audits, this connector lets you handle it all conversationally.
Automates infrastructure checks and quick server restarts without needing to open the terminal or dedicated dashboard.
Monitors resource metrics, manages network configurations, and performs audits across multiple services via simple conversation.
Spins up temporary test environments or verifies the status of managed databases while actively coding a feature.
What Changes When You Connect
Instant Auditing: Need to know which servers are running or how much CPU a specific node is using? Just ask the agent. It pulls metrics instantly, saving you from jumping between monitoring dashboards and your chat window.
Safe Deployment: Don't forget to check prerequisites before deployment. Use list_storages and list_iso_images first. Then, use link_storage_to_server only after confirming the server is powered off via get_server_power.
Network Visibility: Managing IPs and firewalls used to be a nightmare of separate screens. Now, you can ask the agent to list_ips or list_firewalls and understand your network perimeter in one chat exchange.
Lifecycle Control: Forget manual shutdowns. You can issue an ACPI shutdown on a server using shutdown_server, then follow up by checking its status with get_server_power—all without leaving your workflow.
Rapid Provisioning: Need to test something? The agent handles the full flow: list_locations for the right region, then create_server, and finally link_ips to make it accessible.
See it in action
The Weekend Audit
A system administrator needs to check if all 14 staging servers are correctly configured before the Monday release. They prompt their agent: 'List all servers' and then follow up with, 'For those listed, get_server_metrics for CPU usage.' The agent compiles the list and provides a single summary of resource health.
The New Dev Environment
A developer needs a clean test machine. They ask the agent to create_server using a specific template, then immediately run list_networks to ensure it lands in the correct private network segment before linking resources.
Fixing a Broken Service
A production service is unreachable after an update. The engineer asks the agent to check network connectivity by listing all firewalls, identifying which rule broke the port, and then instructing the agent to modify or remove the incorrect rule.
Decommissioning Hardware
The team is retiring old hardware. Instead of manually navigating multiple screens, they prompt the agent to list_servers for all nodes marked 'legacy' and then issue a shutdown_server command on each one sequentially.
The honest tradeoffs
Forgetting prerequisites
A user tries to link storage directly without checking the server status. They run link_storage_to_server, but it fails because they forgot that the target server must be powered off first.
Always check power state first using get_server_power. Then, if needed, use shutdown_server. Only after confirming 'Off' should you attempt to call link_storage_to_server.
Over-relying on listing
The user runs list_servers and sees a server listed but knows it's probably decommissioned. They waste time checking its metrics instead of verifying its status.
After running list_servers, always use get_server_power first to verify the current state before attempting any actions or metric checks.
Mixing network and server calls
The user tries to build a complex setup by manually calling link_ip_to_server and then list_networks, leading to confusion about which resource owns the IP.
Start with an overarching goal. Ask the agent: 'I need a new web server in region X.' The agent will guide you through creating the server (create_server) and linking resources (link_ip_to_server) as one cohesive task.
When It Fits, When It Doesn't
Use this MCP if your workflow requires state changes. If your goal is to create, modify, monitor, or delete a resource—like running 'get_server_metrics' or using 'create_server'—this connector is mandatory. Don't use it if you just need simple read data, like listing the available datacenters via list_locations; in that case, any general API client will suffice. You must use this MCP when your process involves coordinating multiple steps: e.g., getting a server's power status (get_server_power), and then linking storage to it (link_storage_to_server).
Questions you might have
How do I check a server's performance using get_server_metrics? +
You provide the specific server ID to the agent, and it pulls metrics like CPU usage or IOPS. The agent then reports if the machine is operating normally based on that data.
Do I need to shut down a server before linking storage with link_storage_to_server? +
Yes, you do. You should first use get_server_power or shutdown_server to ensure the target server is powered off. The API call for linking storage often requires this prerequisite.
What is the best way to find a new location to deploy my servers? +
Use list_locations first. This gives you all available datacenters or regions where you can reliably provision resources before calling create_server.
Can I check if a server is running using get_server_power? +
Yes, that's the primary function. It gives you the current operational state—on or off—so you know exactly what power level to expect from any given ID.
When I use `create_server`, what key details do I need to provide besides just the CPU and RAM specifications? +
You must specify a valid location UUID and often a template ID. The process requires these context points to build the server correctly, so always run list_locations first to get available options.
If I need to check existing security rules, how do I audit my current network settings using `list_firewalls`? +
list_firewalls pulls up a complete list of all active firewalls and their associated rule sets. This lets you see exactly what traffic is currently allowed or blocked before making any changes.
I want to make sure I'm using the right IP address; how do I check if an IP is available for linking with `list_ips`? +
list_ips retrieves every allocated IP in your account. Reviewing this list helps you verify availability and ensures that when you run link_ip_to_server, the target resource hasn't already been assigned.
How do I get a complete overview of all managed services, like databases or Redis instances, using `list_paas`? +
list_paas gives you an inventory of every Platform as a Service resource attached to your account. This is the fastest way to see and manage database service statuses without guessing.
Can I check the power status of a specific server using its UUID? +
Yes! Use the get_server_power tool with the server's UUID. The agent will return whether the server is currently powered on or off.
How do I monitor the performance of my cloud servers? +
You can use the get_server_metrics tool. It retrieves data in 15-minute intervals for core usage and storage IOPS, allowing your AI to analyze resource consumption.
Does this integration support managed databases like MySQL or PostgreSQL? +
Yes, you can list all managed Platform Services (PaaS) including MySQL, PostgreSQL, and Redis using the list_paas tool.
We've already built the connector for Gridscale. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 17 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.