Robokassa MCP vs Shipstatic MCP

In-depth architectural comparison of the Robokassa MCP and Shipstatic MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Robokassa MCP when:

• You need dedicated capabilities in the Cloud Platforms domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: create_invoice, check_payment, list_currencies.

Explore Robokassa MCP Details

Choose Shipstatic MCP when:

• You need dedicated capabilities in the Cloud Platforms domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: deployments_upload, deployments_list, deployments_get.

Explore Shipstatic MCP Details

Feature & Specification Comparison

Specification	Robokassa MCP Cloud Platforms	Shipstatic MCP shipstatic Cloud Platforms
Summary	Comprehensive MCP server for the Robokassa payment gateway (18 tools, full API coverage).	Deploy and manage static sites from AI agents. A simpler alternative to Vercel and Netlify for static website hosting — upload files, get a URL, and connect custom domains.
Category & Scope	Cloud Platforms

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "robokassa-mcp": {
      "command": "uvx",
      "args": [
        "robokassa-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "shipstatic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@shipstatic/mcp"
      ]
    }
  }
}

Related MCP Server Comparisons