desktop-mate-mcp
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
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 |
|---|---|
| get_directory_overviewB | Return the directory scope and source-verification rules the site publishes. (Desktop Mate) |
| get_official_linksA | Return the canonical list of official links for Desktop Mate (website, support, docs when available). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tell_me_about_desktop_mate | Summarize what the site is, who it's for, and how it works. — Desktop Mate |
| find_a_listing_desktop_mate | Plan a directory search without treating a static snapshot as live status. — Desktop Mate |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| directory | Public directory scope, listing criteria, and source-verification boundaries. |
| faq | Short FAQ generated from public site metadata. |
| links | Canonical URLs to share with users. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one provides directory scope and verification rules, the other returns official links. There is no overlap.
Both tool names follow a consistent 'get_' prefix followed by a noun, adhering to a verb_noun pattern.
With only 2 tools, the server feels too thin for typical MCP interactions. While the tools are focused, the count is low for a full-featured server.
The server lacks any action-oriented tools beyond reading static information, leaving significant gaps for common use cases like managing or interacting with Desktop Mate.