Skip to main content
Glama
enesjakozh
Xutaotaotao

mcp-get-installed-apps

by Xutaotaotao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Obtener aplicaciones instaladas en el servidor MCP

Un servidor de Protocolo de Contexto de Modelo (MCP) que proporciona información sobre las aplicaciones instaladas en su computadora, compatible con MacOS y Windows.

Introducción del proyecto

El servidor MCP para aplicaciones instaladas es una implementación sencilla de MCP que permite a los asistentes de IA descubrir qué aplicaciones están instaladas en su equipo. Este servidor implementa la especificación del Protocolo de Contexto de Modelo (MCP), lo que permite una integración fluida con clientes de IA compatibles.

Related MCP server: XcodeBuildMCP

Características

  • Devuelve una lista completa de las aplicaciones instaladas en su computadora

  • Integración sencilla con cualquier cliente de IA compatible con MCP

  • Implementación ligera con dependencias mínimas

Estructura del proyecto

mcp-get-installed-apps
├── src
│   ├── index.ts               # Application entry point
├── tsconfig.json              # TypeScript configuration file
├── package.json               # npm configuration file
└── README.md                  # Project documentation

Instalación

git clone https://github.com/Xutaotaotao/mcp-get-installed-apps.git
cd git-mcp-server
npm install
npm run build

Configuración de MCP

Después de la instalación, puede configurar Obtener aplicaciones instaladas MCP en su configuración JSON de MCP:

{
    "mcpServers": {
        "get-installed-apps": {
            "command": "node",
            "args": [
                "mcp-get-installed-apps/build/index.js"
            ]
        }
    }
}

Configurar el JSON de MCP en el cliente de IA

Descripción de la herramienta MCP

Obtener aplicaciones instaladas El servidor MCP proporciona la siguiente herramienta, a la que se puede llamar a través del protocolo MCP:

Obtener aplicaciones instaladas (get-installed-apps)

Devuelve una lista de todas las aplicaciones instaladas en su computadora.

Parámetros:

  • Ninguno

Devoluciones:

  • Éxito: Contenido de texto que contiene datos JSON de todas las aplicaciones instaladas

  • Error: Contenido de texto que contiene información de error

Available Tools

1 tool
get-installed-appsB

Get my computer's installed apps

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Get' which implies a read operation, but fails to describe critical traits like whether this requires permissions, what format the output is in, if it's paginated, or any rate limits. For a tool with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It is front-loaded with the core purpose, making it easy for an AI agent to quickly understand the tool's function without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what the return values are (e.g., list format, data structure) or address behavioral aspects like permissions or errors. For a tool that retrieves system data, this leaves significant gaps in understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the inputs. The description does not need to add parameter information, and it appropriately avoids redundancy. A baseline of 4 is applied since no parameters exist, and the description does not introduce confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get my computer's installed apps' clearly states the action (get) and resource (installed apps) with a specific scope (my computer). It's not tautological with the tool name 'get-installed-apps' and provides a meaningful purpose. However, without sibling tools, the differentiation aspect is not applicable, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool, such as prerequisites, alternatives, or exclusions. It simply states what the tool does without context for usage, which is a significant gap in helping an AI agent make informed decisions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedget-installed-apps
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as retrieving installed apps from the computer, making it distinct by default.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'get-installed-apps' follows a clear verb-noun pattern, and there are no other tools to compare it against for inconsistency.

Tool Count2/5

A single tool is too few for most server purposes, as it limits functionality and suggests a thin or incomplete surface. While it might be appropriate for a very narrow scope, it generally feels insufficient for typical agent workflows.

Completeness2/5

The server's domain appears to be managing installed apps, but with only a 'get' operation, there are significant gaps. Missing operations like install, uninstall, update, or search apps make the surface incomplete and likely to cause agent failures for broader tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers