Backtest360 vs Carbone MCP

In-depth architectural comparison of the Backtest360 and Carbone 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 Backtest360 when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: engine_info, get_me, get_catalog.

Explore Backtest360 Details

Choose Carbone MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: convert_document, render_document, list_templates.

Explore Carbone MCP Details

Feature & Specification Comparison

Specification	Backtest360 Developer Tools	Carbone MCP Developer Tools
Summary	MCP server exposing the Backtest360 engine API as tools for AI agents.	Generate PDF/DOCX/XLSX/PPTX from templates+JSON. Convert Office/HTML/MD to PDF. Universal templating
Category & Scope	Developer Tools	Developer Tools
Quality signal

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": {
    "backtest360": {
      "command": "uvx",
      "args": [
        "backtest360-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "carbone-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "carbone-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons