What is the key difference between Ragstack and Tidesman?

Ragstack belongs to the Cloud Platforms category with local stdio execution, while Tidesman belongs to the Cloud Platforms category with local stdio execution.

How do I install Ragstack or Tidesman 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 Ragstack and Tidesman free or paid?

Ragstack operates under a Free / Open Source model (No auth required). Tidesman operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Ragstack lists 0 tools with 0 views and 25 GitHub stars. Tidesman lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Ragstack and Tidesman 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.

How do I install Ragstack or Tidesman in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Ragstack and Tidesman free to use, or do they require API keys?

Ragstack is listed under a Free / Open Source model with No auth required . Tidesman operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Ragstack and Tidesman at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both ragstack and tidesman as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Ragstack has a Quality Score of 43 /100 ( Fair ) with 0 views, 0 installs, and 25 GitHub stars. Tidesman holds a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Ragstack vs Tidesman

In-depth architectural comparison of the Ragstack and Tidesman 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

Ragstack

Cloud Platforms · Local stdio

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

Tidesman

Cloud Platforms · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Ragstack if you need specialized Cloud Platforms tools running via a local process. Choose Tidesman if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

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

Explore Ragstack Details

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

Explore Tidesman Details

Feature & Specification Comparison

Specification	R Ragstack Cloud Platforms	T Tidesman Cloud Platforms
Summary	Search, chat, upload, and scrape a serverless RAGStack knowledge base on AWS.	A free native MCP server for running and debugging Linux containers with Apple's container tool.
Category & Scope	Cloud Platforms	Cloud Platforms
Quality signal

Tools & Capabilities Breakdown

Ragstack Tools (0)

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

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

Ragstack Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ragstack": {
      "command": "uvx",
      "args": [
        "for"
      ]
    }
  }
}

Tidesman Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Ragstack is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Tidesman belongs to Cloud Platforms using local stdio subprocess. Select Ragstack when you need capabilities focused on cloud platforms and Tidesman when you require tools for cloud platforms.

More alternatives to Ragstack More alternatives to Tidesman Cloud Platforms category hub