cursor_mcp_installer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| install_repo_mcp_serverC | Install an MCP server via npx or uvx |
| install_local_mcp_serverC | Install an MCP server whose code is cloned locally on your computer |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.