Make MCP Server Generic Rather Than Claude Desktop-Specific

[Zane-XY]

The MCP server should function as a generic host for tools accessible to all MCP clients. Currently, the implementation appears to be overly coupled with Claude Desktop specifically, rather than serving as a universal tool provider.

Issues identified:

• The server explicitly checks for Claude Desktop installation
• It throws an error ("Claude Client is not installed") when Claude Desktop isn't found
• The implementation emphasizes its relationship with Claude Desktop rather than being client-agnostic

Requested Changes

Please modify the implementation to be a passive MCP Server that:

• Can be discovered through HTTP
• Operates independently without requiring a stdio proxy
• Serves tools to any compatible MCP client without Claude Desktop dependency

This would align with the broader vision of having a versatile MCP server that provides tools to the entire MCP client ecosystem rather than serving a single specific client.