F
licenseA
qualityD
maintenanceA universal MCP server that integrates any API with Claude Desktop by pointing it at a Swagger/OpenAPI spec, automatically generating tools for interaction.
3
44
-
claude-desktop-mcp
by dmccaffery
Related Servers
Alternatives to claude-desktop-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server with example tools for arithmetic and greeting, designed for deployment on Amazon Bedrock AgentCore Runtime with OAuth authentication.4-
- AlicenseAqualityDmaintenanceA demonstration MCP server for educational purposes, showcasing how to build and integrate MCP servers with LLM clients like Claude Desktop.1MIT
- FlicenseCqualityDmaintenanceA server built with mcp-framework that allows users to extend Claude's capabilities by adding custom tools that can be used through the Claude Desktop client.378 npm-
- AlicenseNot gradedqualityDmaintenanceA real, runnable MCP server exposing three read-only tools (inventory, pricing, hours) with a CLI agent that lets Claude discover and call them.MIT
- FlicenseNot gradedqualityBmaintenanceA custom MCP server exposing database, ticketing, and external-API tools to both Claude Desktop and a self-built autonomous agent powered by Groq's free-tier LLaMA 3.3.-
TDQS
B3.4/5.0
Scored across 50 tools
Disambiguation5/5
Each tool has a distinct domain prefix and action-object pairing, making them clearly separable. Even within similar operations (e.g., users_set_user_role vs users_update_user), the intent is unambiguous.
Naming Consistency5/5
All tools follow a consistent {domain}_{verb}_{object} naming convention in lowercase snake_case. Verbs like list, get, create, update, delete are used uniformly across domains.
Tool Count2/5
With 50 tools spanning six different domains, the server is overloaded. While each domain is well-covered, the overall count exceeds what an agent can efficiently navigate and would be better split into separate servers.
Completeness4/5
Each domain provides comprehensive CRUD and lifecycle operations. Minor gaps exist, such as GitHub lacking a single-PR detail fetch or Slack lacking message deletion, but core workflows are fully supported.
Maintenance
ActivityInactive
ResponsivenessNo issues