# Gyro MCP server: connect Claude, Cursor and VS Code to your Gyro account

https://www.gyrohosting.com/en/knowledgebase/article/gyro-mcp-sunucusu

- **What you will learn**: how to add the Gyro MCP server to your AI assistant, let it search the Gyro docs and manage your account safely with your own API key.
- **Time**: 5 minutes

## 1. What is MCP and what does the Gyro MCP server do?

The Model Context Protocol (MCP) is an open standard that connects AI assistants to tools. The Gyro MCP server (`@gyro-hosting/mcp`, open source) runs on your computer and gives your assistant two kinds of tools:

| Tools | What they do | API key |
| --- | --- | --- |
| Docs tools | Search the Gyro developer docs, the full description of an API endpoint, product list, account limits | Not needed |
| Account tools | Services, cloud servers, container environments and logs, S3 buckets, DNS records, balance; with your confirmation power, scaling, DNS records, orders and deletes | Your own key |

The assistant only sees your account: every call is made with your key.

## 2. Create an API key

1. In the client area open the account menu (top right) → **API Credentials**.
2. Create a key. Start with read scopes only (`cloud_read`, `services_read`, `billing_read`). Add write scopes if the assistant should change things, and `cloud_order` if it may place orders.
3. Add your computer's IP address to the allow list.
4. The key is shown once; store it in your password manager.

Skip this step if you only want the docs tools.

## 3. Add it to your assistant

**Claude Desktop** (Settings → Developer → Edit Config), **Cursor** (`~/.cursor/mcp.json`) and similar clients:

```
{
  "mcpServers": {
    "gyro": {
      "command": "npx",
      "args": ["-y", "@gyro-hosting/mcp"],
      "env": { "GYRO_TOKEN": "wck_..." }
    }
  }
}
```

**Claude Code:**

```
claude mcp add gyro --env GYRO_TOKEN=wck_... -- npx -y @gyro-hosting/mcp
```

**VS Code** (`.vscode/mcp.json`; the key is asked once):

```
{
  "inputs": [{ "type": "promptString", "id": "gyro-token", "description": "Gyro API key", "password": true }],
  "servers": {
    "gyro": { "type": "stdio", "command": "npx", "args": ["-y", "@gyro-hosting/mcp"], "env": { "GYRO_TOKEN": "${input:gyro-token}" } }
  }
}
```

Restart the assistant; `gyro` appears in the tool list. Try: *"Which services do I have at Gyro?"*

### No install: remote endpoint

If you do not want to install Node.js, use the endpoint Gyro hosts for you: **`https://mcp.gyrohosting.com/mcp`** (Streamable HTTP). Send your key in the `Authorization: Bearer wck_…` header; without it only the docs tools work.

**Claude Code:**

```
claude mcp add --transport http gyro https://mcp.gyrohosting.com/mcp --header "Authorization: Bearer wck_..."
```

**Cursor** (`~/.cursor/mcp.json`):

```
{ "mcpServers": { "gyro": { "type": "http", "url": "https://mcp.gyrohosting.com/mcp", "headers": { "Authorization": "Bearer wck_..." } } } }
```

**Claude.ai / Claude Desktop custom connector:** Settings → Connectors → Add custom connector → URL `https://mcp.gyrohosting.com/mcp`. A key cannot be sent this way, so you get the docs tools only; for account tools use Claude Code, Cursor, VS Code or the local setup.

**If your key is locked to IP addresses,** requests to the Gyro API come from the endpoint's addresses below; add them to the key's allow list (or create a separate key for the remote endpoint): `45.87.174.151`, `45.87.174.153`, `45.87.174.154`.

The endpoint allows about 120 requests per minute per key, 300 per IP address and 256 KB per request; the API limits apply as well. Your key is not stored or logged; each request is handled on its own.

## 4. Safety: money and deletes need you

- **Tools that change something** (power, scaling, DNS records, buckets) do nothing without `confirm: true`; the assistant is told to ask you first.
- **Tools that spend money** (server, container environment, storage orders) return a **price quote** first. After you agree, the order is paid from your balance; an idempotency key makes sure the same request never orders twice.
- **Irreversible tools** (delete server, delete DNS record, delete container service) are marked destructive; your MCP client asks before running them.
- **Your key** is never logged or returned; secret fields such as passwords are masked in answers.
- **Prompt injection:** server names, logs and ticket text can contain text written by others. Every result is marked as untrusted data. Keep write and delete scopes off unless you need them.

## 5. Example prompts

- "Which of my cloud servers are stopped?"
- "Show the last 50 log lines of the api service in container environment 12345."
- "How much would a standart-2-4 server in Istanbul cost per month?" (price quote only)
- "Add an A record www → 203.0.113.10 to example.com."
- "How do I connect my GitHub repository to Gyro Pipeline?" (docs search)

## 6. Frequently asked questions

**Can I use it without a key?**

Yes. Without a key only the docs tools work; nothing in your account is read or changed.

**Can the assistant order something without me knowing?**

No. Order tools only return a price quote without `confirm`. If your key has no `cloud_order` scope, ordering is impossible.

**Which limits apply?**

The API limits: 60 requests per minute per key by default and a daily cap on paid operations. All limits: [Account limits](https://www.gyrohosting.com/developers/en/guides/account-limits.html).

**Is there a hosted (remote) MCP endpoint?**

Yes: `https://mcp.gyrohosting.com/mcp`. Nothing to install; see "No install: remote endpoint" in section 3.

> **Did you know?**
> 
> Your assistant can also read the whole Gyro API: the OpenAPI description is on the [OpenAPI page of the developer docs](https://www.gyrohosting.com/developers/en/openapi.html).

## Next steps

- MCP setup and the tool list: [Gyro developer docs: MCP](https://www.gyrohosting.com/developers/en/mcp.html)
- First API request: [Gyro developer docs: Getting started](https://www.gyrohosting.com/developers/en/guides/start.html)