MCP (Model Context Protocol) server for managing Servers.com dedicated server infrastructure.
{
"mcpServers": {
"serverscom-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP (Model Context Protocol) server for managing Servers.com dedicated server infrastructure.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 20 days ago. 1 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for Serverscom Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP (Model Context Protocol) server for managing Servers.com dedicated server infrastructure. Enables AI assistants (Claude, etc.) to interact with the Servers.com API directly — query servers, manage SSH keys, configure networks, manage L2 segments, provision Remote Block Storage, reinstall operating systems, and more.
npx @servers.com/mcp --token your-api-token
# or via env var
SC_TOKEN=your-api-token npx @servers.com/mcp
{
"mcpServers": {
"serverscom": {
"command": "npx",
"args": ["-y", "@servers.com/mcp"],
"env": {
"SC_TOKEN": "your-api-token"
}
}
}
}
| Flag | Env var | Required | Default | Description |
|---|---|---|---|---|
| --token, -t | SC_TOKEN | yes | — | Servers.com API token |
| --endpoint, -e | SC_ENDPOINT | no | https://api.servers.com/v1 | Custom API endpoint |
73 tools across 6 categories — see TOOLS.md for the full reference.
Many operations are asynchronous. After calling them, poll the relevant status field:
| Operation | Poll with | Field to watch |
|---|---|---|
| Feature changes | list_dedicated_server_features | feature status |
| Rescue mode | get_dedicated_server | operational_status |
| OS reinstallation | get_dedicated_server | operational_status |
| Power changes | get_dedicated_server | power_status |
operational_status values: normal → provisioning → installation → entering_rescue_mode → rescue_mode → exiting_rescue_mode → maintenance
go build -o serverscom-mcp .
Releases are automated via GoReleaser and GitHub Actions. Push a version tag to trigger the pipeline:
git tag v1.2.3
git push origin v1.2.3
The workflow will:
@servers.com/mcp and platform packages to npm using trusted publishing (OIDC, no long-lived tokens)serverscom-mcp/
├── main.go # Entry point
└── internal/tools/
├── tools.go # Tool registration hub, shared helpers
├── hosts.go # list_hosts
├── dedicated_servers.go # Server CRUD and feature management
├── ssh_keys.go # SSH key operations
├── locations.go # Location and infrastructure options
├── power.go # Power management
├── drives.go # Drive slot listing
├── reinstall.go # OS reinstallation
├── networks.go # Network management
├── l2_segments.go # L2 segment management
└── rbs.go # Remote Block Storage