Skip to main content
Glama
enesjakozh
Xutaotaotao

mcp-get-installed-apps

by Xutaotaotao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

获取已安装的应用程序 MCP 服务器

模型上下文协议 (MCP) 服务器提供有关计算机上已安装应用程序的信息，支持 MacOS 和 Windows。

项目介绍

获取已安装的应用程序 MCP 服务器是一个简单的 MCP 实现，允许 AI 助手发现您的计算机上安装了哪些应用程序。该服务器实现了模型上下文协议 (MCP) 规范，可与兼容的 AI 客户端无缝集成。

Related MCP server: XcodeBuildMCP

特征

  • 返回计算机上已安装应用程序的完整列表

  • 与任何兼容 MCP 的 AI 客户端简单集成

  • 具有最小依赖性的轻量级实现

项目结构

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

安装

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

MCP 配置

安装后，您可以在 MCP JSON 配置中配置“获取已安装的应用程序”MCP：

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

在 AI 客户端中配置 MCP JSON

MCP 工具描述

获取已安装的应用程序 MCP 服务器提供以下工具，可以通过 MCP 协议调用：

获取已安装的应用程序（get-installed-apps）

返回计算机上已安装的所有应用程序的列表。

参数：

  • 没有任何

返回：

  • 成功：包含所有已安装应用程序的 JSON 数据的文本内容

  • 失败：包含错误信息的文本内容

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