Robokassa MCP vs Anytype (self Hosted HTTP)

In-depth architectural comparison of the Robokassa MCP and Anytype (self Hosted HTTP) 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 Anytype (self Hosted HTTP) when:

• You need dedicated capabilities in the Cloud Platforms domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Anytype (self Hosted HTTP) Details

Feature & Specification Comparison

Specification	Robokassa MCP Cloud Platforms	Anytype (self Hosted HTTP) Cloud Platforms
Summary	Comprehensive MCP server for the Robokassa payment gateway (18 tools, full API coverage).	Self-hosted Anytype MCP server: the full Anytype API as an always-on Docker + HTTP endpoint.
Category & Scope	Cloud Platforms	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": {
    "anytype-self-hosted-http": {
      "url": "http://localhost:8769/mcp"
    }
  }
}

Related MCP Server Comparisons