cursor_mcp_installer
Related Servers
Alternatives to cursor_mcp_installer
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Cursor IDE that simplifies the installation and configuration of other MCP servers.38 npm77MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides detailed information about your development environment to the Cursor code editor, enabling more context-aware assistance.7MIT
- AlicenseNot gradedqualityDmaintenanceA simple MCP server to discover and manage MCP servers. Provides tools to find, add, list, and remove MCP server configurations for Cursor.5 npm8MIT
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP tool for directory tree visualization in Cursor, with smart filtering and customizable ignore/keep patterns.MIT
- FlicenseAqualityCmaintenanceEnables MCP clients like Cursor to manage local CurseForge Minecraft instances by creating world-specific mod profiles, editing configs, diagnosing crashes, and applying changes on disk before launching the game.21-
- FlicenseNot gradedqualityDmaintenanceMCP Server to log time and view Jira statistics directly from Cursor IDE.-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one installs MCP servers from local code, while the other installs them via package managers (npx/uvx). There is no overlap or ambiguity between these installation methods, making it easy for an agent to select the correct tool based on the source of the server.
Both tools follow a consistent verb_noun pattern with 'install' as the verb and descriptive suffixes ('local_mcp_server', 'repo_mcp_server'). The naming is uniform and predictable, using snake_case throughout, which aids in clarity and usability.
With only 2 tools, the server feels thin for an installer purpose, as it might lack operations like uninstalling, listing installed servers, or updating. While the tools cover basic installation scenarios, the limited count suggests incomplete functionality for managing MCP servers comprehensively.
The tool surface is significantly incomplete for an installer domain. It only provides installation methods but lacks essential operations such as uninstallation, listing installed servers, updating servers, or checking installation status. This creates gaps that could lead to agent failures when trying to manage MCP servers beyond initial setup.