@servers.com/mcp_linux_amd64 0.1.0 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -5,63 +5,14 @@ MCP (Model Context Protocol) server for managing [Servers.com](https://servers.c
5
5
  ## Quick Start
6
6
 
7
7
  ```bash
8
- # run directly with npx (no install required)
9
8
  npx @servers.com/mcp --token your-api-token
10
9
 
11
10
  # or via env var
12
11
  SC_TOKEN=your-api-token npx @servers.com/mcp
13
12
  ```
14
13
 
15
- ## Requirements
16
-
17
- - Servers.com API token
18
-
19
- ## Releasing
20
-
21
- Releases are fully automated via [GoReleaser](https://goreleaser.com) and GitHub Actions.
22
-
23
- Push a version tag to trigger the pipeline:
24
-
25
- ```bash
26
- git tag v1.2.3
27
- git push origin v1.2.3
28
- ```
29
-
30
- The workflow (`.github/workflows/release.yml`) will:
31
- 1. Build binaries for Linux, macOS, Windows (amd64 + arm64)
32
- 2. Create a GitHub Release with archives and checksums
33
- 3. Publish `@servers.com/mcp` and platform packages to npm via [`goreleaser-npm-publisher`](https://github.com/evg4b/goreleaser-npm-publisher)
34
-
35
- **Required repository secrets:**
36
- - `NPM_TOKEN` — npm automation token with publish access
37
-
38
- ## Building from source
39
-
40
- ```bash
41
- go build -o serverscom-mcp .
42
- ```
43
-
44
- ## Configuration
45
-
46
- Flags can be set via CLI flags or environment variables:
47
-
48
- | Flag | Env var | Required | Default | Description |
49
- |---|---|---|---|---|
50
- | `--token`, `-t` | `SC_TOKEN` | yes | — | Servers.com API token |
51
- | `--endpoint`, `-e` | `SC_ENDPOINT` | no | `https://api.servers.com/v1` | Custom API endpoint |
52
-
53
- ```bash
54
- # via env vars
55
- SC_TOKEN=your-token ./serverscom-mcp
56
-
57
- # via flags
58
- ./serverscom-mcp --token your-token --endpoint https://api.servers.com/v1
59
- ```
60
-
61
14
  ## Usage with Claude Desktop
62
15
 
63
- ### via npx (recommended)
64
-
65
16
  ```json
66
17
  {
67
18
  "mcpServers": {
@@ -76,20 +27,12 @@ SC_TOKEN=your-token ./serverscom-mcp
76
27
  }
77
28
  ```
78
29
 
79
- ### via local binary
30
+ ## Configuration
80
31
 
81
- ```json
82
- {
83
- "mcpServers": {
84
- "serverscom": {
85
- "command": "/path/to/serverscom-mcp",
86
- "env": {
87
- "SC_TOKEN": "your-api-token"
88
- }
89
- }
90
- }
91
- }
92
- ```
32
+ | Flag | Env var | Required | Default | Description |
33
+ |---|---|---|---|---|
34
+ | `--token`, `-t` | `SC_TOKEN` | yes | — | Servers.com API token |
35
+ | `--endpoint`, `-e` | `SC_ENDPOINT` | no | `https://api.servers.com/v1` | Custom API endpoint |
93
36
 
94
37
  ## Available Tools
95
38
 
@@ -203,15 +146,41 @@ Many operations are asynchronous. After calling them, poll the relevant status f
203
146
  | OS reinstallation | `get_dedicated_server` | `operational_status` |
204
147
  | Power changes | `get_dedicated_server` | `power_status` |
205
148
 
206
- ### `operational_status` values
149
+ `operational_status` values: `normal` → `provisioning` → `installation` → `entering_rescue_mode` → `rescue_mode` → `exiting_rescue_mode` → `maintenance`
207
150
 
208
- `normal` → `provisioning` → `installation` → `entering_rescue_mode` → `rescue_mode` → `exiting_rescue_mode` → `maintenance`
151
+ ## License
209
152
 
210
- ## Project Structure
153
+ [MIT](LICENSE)
154
+
155
+ ---
156
+
157
+ ## Development
158
+
159
+ ### Building from source
160
+
161
+ ```bash
162
+ go build -o serverscom-mcp .
163
+ ```
164
+
165
+ ### Releasing
166
+
167
+ Releases are automated via [GoReleaser](https://goreleaser.com) and GitHub Actions. Push a version tag to trigger the pipeline:
168
+
169
+ ```bash
170
+ git tag v1.2.3
171
+ git push origin v1.2.3
172
+ ```
173
+
174
+ The workflow will:
175
+ 1. Build binaries for Linux, macOS, Windows (amd64 + arm64)
176
+ 2. Create a GitHub Release with archives and checksums
177
+ 3. Publish `@servers.com/mcp` and platform packages to npm using [trusted publishing](https://docs.npmjs.com/trusted-publishers/) (OIDC, no long-lived tokens)
178
+
179
+ ### Project Structure
211
180
 
212
181
  ```
213
182
  serverscom-mcp/
214
- ├── main.go # Entry point: MCP server setup, env config
183
+ ├── main.go # Entry point
215
184
  └── internal/tools/
216
185
  ├── tools.go # Tool registration hub, shared helpers
217
186
  ├── hosts.go # list_hosts
@@ -223,7 +192,3 @@ serverscom-mcp/
223
192
  ├── reinstall.go # OS reinstallation
224
193
  └── networks.go # Network management
225
194
  ```
226
-
227
- ## License
228
-
229
- See [LICENSE](LICENSE).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@servers.com/mcp_linux_amd64",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "bin": {
5
5
  "mcp_linux_amd64": "serverscom-mcp"
6
6
  },
package/serverscom-mcp CHANGED
Binary file