What is the key difference between Lathe and Kubeshark?

Lathe belongs to the Databases category with cloud HTTP/SSE execution, while Kubeshark belongs to the Databases category with cloud HTTP/SSE execution.

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

Lathe operates under a Free / Open Source model (No auth required). Kubeshark operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Lathe lists 0 tools with 0 views and 0 GitHub stars. Kubeshark lists 0 tools with 0 views and 12,072 GitHub stars.

Can I use both Lathe and Kubeshark 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

Lathe vs Kubeshark

In-depth architectural comparison of the Lathe and Kubeshark 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

Lathe

Databases · Remote HTTP/SSE

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

Kubeshark

Databases · Remote HTTP/SSE

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

Verdict Summary: Choose Lathe if you need specialized Databases tools running via a hosted cloud SSE transport. Choose Kubeshark if your workspace requires Databases integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Lathe when:

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

Explore Lathe Details

Choose Kubeshark when:

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

Explore Kubeshark Details

Feature & Specification Comparison

Specification	L Lathe Databases	Kubeshark kubeshark Databases
Summary	Managed Postgres, Redis, CouchDB and NATS on a dedicated EU machine, one flat price.	Real-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.
Category & Scope	Databases	Databases
Quality signal

Tools & Capabilities Breakdown

Lathe Tools (0)

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

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

Lathe Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "lathe": {
      "url": "https://lathe.computer/agents"
    }
  }
}

Kubeshark Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-304": {
      "url": "https://raw.githubusercontent.com/kubeshark/assets/master/svg/kubeshark-logo.svg"
    }
  }
}

Frequently Asked Questions

Lathe is categorized under Databases and uses a remote streaming HTTP/SSE transport. In contrast, Kubeshark belongs to Databases using remote streaming HTTP/SSE transport. Select Lathe when you need capabilities focused on databases and Kubeshark when you require tools for databases.

More alternatives to Lathe More alternatives to Kubeshark Databases category hub