DesktopInsights
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DESKTOPINSIGHTS_API_KEY | Yes | Your API key from desktopinsights.com/settings/api | |
| DESKTOPINSIGHTS_API_URL | No | The base URL for the Desktop Insights API | https://desktopinsights.com |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_appA | Look up what SDKs, frameworks, and dependencies a specific desktop application uses. Returns the full technology stack including error tracking, analytics, UI framework, payments, and 7 other SDK categories, plus detailed dependency list with versions. Accepts app names (e.g., "Figma", "Slack", "1Password") or bundle IDs (e.g., "com.figma.Desktop"). Covers 12,000+ macOS and Windows apps. |
| search_appsA | Search for desktop applications by SDK usage, runtime, platform, or developer. Use this to find which apps use a specific SDK (e.g., "Which apps use Sentry?"), discover technology adoption patterns, or research a developer's products. Supports all 11 SDK categories, runtime (electron/native/qt/flutter), platform (macos/windows), and developer name. Pass "null" as an SDK value to find apps without that SDK type. At least one filter is required. |
| compare_appsA | Compare the technology stacks of two desktop applications side by side. Shows SDK differences, shared technologies, and metadata comparison. Useful for competitive analysis (e.g., "Compare Figma vs Sketch", "Compare Slack vs Discord"). Uses 2 API calls. |
| list_sdk_categoriesA | List all 11 SDK categories tracked by Desktop Insights with their API field names and example SDKs for each. Use this to discover what filters are available for search_apps, or to understand the sdkSummary fields returned by lookup_app. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-stack | Analyze the technology stack of a desktop application |
| competitive-analysis | Compare technology stacks of two competing desktop applications |
| sdk-adoption | Research adoption of a specific SDK across desktop applications |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| sdk-categories | All 11 SDK categories tracked by Desktop Insights with field names and examples |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: compare_apps for side-by-side analysis, list_sdk_categories for metadata discovery, lookup_app for detailed app technology inspection, and search_apps for filtered app discovery. There is no overlap in functionality, and the descriptions explicitly differentiate their use cases, preventing agent misselection.
All tool names follow a consistent verb_noun pattern with snake_case: compare_apps, list_sdk_categories, lookup_app, and search_apps. The verbs (compare, list, lookup, search) accurately reflect the actions, and the nouns (apps, sdk_categories, app) align with the domain, creating a predictable and readable naming convention throughout.
With 4 tools, this server is well-scoped for its purpose of desktop application technology analysis. Each tool earns its place by covering distinct aspects: metadata listing, app lookup, search with filters, and comparison. The count is neither too thin nor bloated, fitting the domain's core workflows efficiently.
The tool surface provides comprehensive coverage for technology stack analysis, including discovery (list_sdk_categories), inspection (lookup_app), search (search_apps), and comparison (compare_apps). A minor gap exists in update or management operations (e.g., adding new apps or SDKs), but this is reasonable for a read-only analysis server, and agents can work around it with the provided tools.