What is the key difference between AutoTS and Classifier.dev?

AutoTS belongs to the Data Science Tools category with local stdio execution, while Classifier.dev belongs to the Data Science Tools category with local stdio execution.

How do I install AutoTS or Classifier.dev in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are AutoTS and Classifier.dev free or paid?

AutoTS operates under a Free / Open Source model (No auth required). Classifier.dev operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

AutoTS lists 0 tools with 3 views and 1,429 GitHub stars. Classifier.dev lists 0 tools with 0 views and 423 GitHub stars.

Can I use both AutoTS and Classifier.dev together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

AutoTS vs Classifier.dev

In-depth architectural comparison of the AutoTS and Classifier.dev 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.

At a Glance & Executive Verdict

AutoTS

Data Science Tools · Local stdio

Quality: 45/100 (Fair) | Auth: No auth required

Classifier.dev

Data Science Tools · Local stdio

Quality: 36/100 (Fair) | Auth: No auth required

Verdict Summary: Choose AutoTS if you need specialized Data Science Tools tools running via a local process. Choose Classifier.dev if your workspace requires Data Science Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose AutoTS when:

You need dedicated capabilities in the Data Science Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore AutoTS Details

Choose Classifier.dev when:

You need dedicated capabilities in the Data Science Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Classifier.dev Details

Feature & Specification Comparison

Specification	AutoTS Data Science Tools	Classifier.dev Data Science Tools
Summary
Category & Scope	Data Science Tools	Data Science Tools
Quality signal

Tools & Capabilities Breakdown

AutoTS Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Classifier.dev Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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).

AutoTS Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "autots": {
      "command": "uvx",
      "args": [
        "autots"
      ]
    }
  }
}

Classifier.dev Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "classifier-dev": {
      "command": "npx",
      "args": [
        "-y",
        "classifier-dev"
      ]
    }
  }
}

Frequently Asked Questions

AutoTS is categorized under Data Science Tools and uses a local stdio subprocess. In contrast, Classifier.dev belongs to Data Science Tools using local stdio subprocess. Select AutoTS when you need capabilities focused on data science tools and Classifier.dev when you require tools for data science tools.

More alternatives to AutoTS More alternatives to Classifier.dev Data Science Tools category hub