Skip to main content
Glama
rocnubie

desktop-mate-mcp

by rocnubie
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Desktop Mate MCP Server

Desktop Mate: Download, Mods & Character | Desktop Mate

MCP Badge License: MIT Zero Config Node MCP Stdio Transport

A Model Context Protocol server that exposes the canonical Desktop Mate knowledge surface — directory listings, source evidence, and official links, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.

Official website: https://desktop-mate.com

🗂️ About Desktop Mate

Desktop Mate is an independent community guide for finding Desktop Mate downloads, platform details, characters, and mod sources. It links to verified publisher, Steam, and mod destinations so visitors can choose the appropriate official or community page.

The site is a static guide and does not host Desktop Mate, DLC, mods, or character files. This MCP exposes the guide's documented scope and canonical website as read-only context; it cannot install software, inspect a mod, or guarantee that an external download remains available.

Desktop Mate is not affiliated with infiniteloop, Valve/Steam, or character rights holders. Use the linked destinations and their own terms when downloading or using third-party content.

Related MCP server: docs-mcp-server

Tools

get_directory_overview

Return the directory scope and source-verification rules the site publishes. (Desktop Mate)

Input: no parameters. Returns: text/markdown.

get_official_links

Return the canonical list of official links for Desktop Mate (website, support, docs when available).

Input: no parameters. Returns: text/markdown.

Resources

  • site://desktop-mate/directory — Public directory scope, listing criteria, and source-verification boundaries.

  • site://desktop-mate/faq — Short FAQ generated from public site metadata.

  • site://desktop-mate/links — Canonical URLs to share with users.

Prompts

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

Installation

Install via Smithery

npx -y @smithery/cli install desktop-mate-mcp --client claude

(Replace claude with cursor, windsurf, or continue for those clients.)

Install from source

git clone https://github.com/rocnubie/desktop-mate-mcp.git
cd desktop-mate-mcp
pnpm install

Then add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):

{
  "mcpServers": {
    "desktop-mate-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/desktop-mate-mcp/src/index.mjs"
      ]
    }
  }
}

Debug with MCP Inspector

npx @modelcontextprotocol/inspector node src/index.mjs

Official Links

Development

pnpm install
pnpm start                 # run the server over stdio

License

MIT

Available Tools

2 tools
get_directory_overviewB

Return the directory scope and source-verification rules the site publishes. (Desktop Mate)

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 must fully disclose behavioral traits. It only states that the tool returns information, but does not mention whether it is read-only, has side effects, requires authentication, or any other behavioral characteristics.

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

Conciseness4/5

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

The description is a single sentence, concise and front-loaded with the action and resource. The parenthetical '(Desktop Mate)' adds minor context but could be clearer.

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

Completeness3/5

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

Without an output schema, the description should fully explain the return value. It mentions 'directory scope and source-verification rules' but does not detail the structure or format, leaving some ambiguity. Adequate but not thorough.

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?

There are no parameters, so the schema coverage is 100% by default. The description adds context about what the tool returns, which is sufficient given the absence of parameters. Baseline 4 is appropriate.

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 verb 'Return' and resource 'directory scope and source-verification rules' clearly state the tool's function. It implicitly distinguishes from sibling 'get_official_links' by focusing on scope/rules vs. links, but does not explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives. The sibling tool is mentioned in context but the description does not state when one should be preferred over the other, nor does it provide any usage context.

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. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedget_directory_overview
    • First observedget_official_links
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one provides directory scope and verification rules, the other returns official links. There is no overlap.

Naming Consistency5/5

Both tool names follow a consistent 'get_' prefix followed by a noun, adhering to a verb_noun pattern.

Tool Count2/5

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.

Completeness2/5

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.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • docs-mcp-server

    DewminK
    F
    license
    Not graded
    quality
    B
    maintenance
    MCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.
    -

  • local-tools-mcp-server

    fenhuayue
    F
    license
    A
    quality
    C
    maintenance
    A read-only MCP server that enables AI assistants to search files, list directories, retrieve system info, and get file metadata on the local file system.
    4
    -

  • Home File Agent

    nfedunwork-code
    F
    license
    Not graded
    quality
    C
    maintenance
    MCP server that provides secure read-only access to a local folder, enabling file listing, reading, semantic search (RAG), and indexing status via natural language, integrated with Claude Desktop and a custom agent loop.
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/desktop-mate-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server