upcloud-mcp-server

A Model Context Protocol (MCP) server intended to integrate with Upcloud APIs to expose tools for retrieving information about Upcloud account, managed databases, servers, and Kubernetes resources.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Infrastructure mcp upcloud automation infrastructure api-integration go
⚙ Agent Friendliness
34
/ 100
Can an agent use this?
🔒 Security
41
/ 100
Is it safe for agents?
⚡ Reliability
12
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
35
Documentation
45
Error Messages
0
Auth Simplicity
55
Rate Limits
0

🔒 Security

TLS Enforcement
60
Auth Strength
40
Scope Granularity
10
Dep. Hygiene
40
Secret Handling
55

Uses credentials passed via environment variables (better than hardcoding, but the README does not describe redaction/logging behavior or secret management practices). No details are provided about least-privilege/scopes or secure transport requirements, and the project maturity is marked as work in progress.

⚡ Reliability

Uptime/SLA
0
Version Stability
20
Breaking Changes
20
Error Recovery
10
AF Security Reliability

Best When

You want an MCP-compatible way to read-only explore Upcloud resources while developing prototypes or internal tooling.

Avoid When

You need a mature, well-documented, production-ready MCP server with strong operational guarantees, documented error/retry semantics, and clearly defined pagination/rate-limit behavior.

Use Cases

  • Querying Upcloud account details (current user or by username).
  • Fetching managed database information by UUID.
  • Listing and retrieving server details by UUID.
  • Listing Kubernetes clusters and retrieving cluster details by UUID.
  • Retrieving Kubernetes plan information.

Not For

  • Production/mission-critical automation (the README explicitly marks it as work in progress and not ready).
  • Use cases requiring webhooks, realtime updates, or event-driven workflows (not mentioned).
  • Environments that cannot securely provide credentials via environment variables.

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: UPCLOUD_USERNAME / UPCLOUD_PASSWORD via environment variables
OAuth: No Scopes: No

Authentication approach is described only at a high level (environment variables). No scope granularity, token lifetimes, or supported auth flows are documented in the provided README.

Pricing

Free tier: No
Requires CC: No

No pricing information is provided in the README (it appears to be an open-source tool; costs would primarily come from Upcloud API usage and your hosting).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • README states the project is work in progress and not ready for use; behavior, edge cases, and reliability may be unstable.
  • No documentation is provided for pagination, rate limiting, or how to handle API throttling within the MCP server.
  • Authentication is via environment variables; agents must ensure secrets are not exposed in logs and are provided correctly in the runtime/container.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for upcloud-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered