1. Conduid
  2. Developer Tools
  3. Dev Tools
MCP server · Developer Tools

Dev Tools

MCP server: Dev Tools

Unclaimed MIT last commit 8 months ago devtools
49Fair

Scored 4 months ago · breakdown

About Dev Tools

Dev Tools is an MCP server published by ssv555 in the Developer Tools category: mCP server: Dev Tools. It has been installed 0 times through Conduid.

Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx mcp-server-dev-tools

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Dev Tools

Powered by Claude · Grounded in docs

I know everything about Dev Tools. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

MCP Desktop Automation

A Model Context Protocol server and toolkit for desktop automation. It provides two main layers of functionality:

  1. Node.js MCP Server: General purpose tools for screen capture, mouse/keyboard control.
  2. PowerShell Scripts: specialized, robust automation for Telegram Desktop (handling encoding, window focus, etc.).

Configuration

Here's how to configure Claude Desktop to use this MCP server.

Local Development (Recommended)

Since you are running this from source:

{
  "mcpServers": {
    "desktop-automation": {
      "command": "node",
      "args": ["D:\\Data\\Documents\\Programming\\Projects\\MCP\\mcp-desktop-automation\\server.js"]
    }
  }
}

NPX (If published)

{
  "mcpServers": {
    "desktop-automation": {
      "command": "npx",
      "args": ["-y", "mcp-desktop-automation"]
    }
  }
}

Permissions

This server requires system-level permissions to:

  • Capture screenshots of your screen
  • Control mouse movement and clicks
  • Simulate keyboard input

Telegram Automation (PowerShell)

The core automation logic for Telegram resides in the scripts/ directory. These are optimized for Windows/PowerShell execution.

1. Send Message to Current Chat (send_telegram_v7.ps1)

Sends a text message to the currently open chat in Telegram.

Usage:

.\scripts\send_telegram_v7.ps1 -Message "Your Message Here"

For Non-ASCII Characters (Cyrillic, Emojis): CRITICAL: To avoid encoding issues in the shell, encode your message in Base64 (UTF-8) and use the -Base64 switch.

# Example: Sending "Привет 🌍"
# Base64 for "Привет 🌍" is "0J/RgNC40LLQtdGCIPCfjI0="
.\scripts\send_telegram_v7.ps1 -Message "0J/RgNC40LLQtdGCIPCfjI0=" -Base64

2. Search Contact and Send Message (send_telegram_search_send.ps1)

Searches for a user/chat, opens it, and sends a message.

Usage:

.\scripts\send_telegram_search_send.ps1 -SearchTerm "John Doe" -Message "Hello"

With Base64 (Recommended for complexity):

.\scripts\send_telegram_search_send.ps1 -SearchTerm "Vladimir" -Message "Base64EncodedString..." -Base64

Process Flow:

  1. Focuses Telegram.
  2. Clicks the "Search" bar (top left).
  3. Types the -SearchTerm.
  4. Clicks the first result.
  5. Clicks the message input field.
  6. Pastes and sends the -Message.
  7. Saves a screenshot to .tmp/ for verification.

Node.js Server Components

The server.js provides the following tools for general automation:

  • screen_capture: Captures the current screen content.
  • keyboard_press: Presses a keyboard key (e.g., 'enter', 'a', 'control').
  • keyboard_type: Types text at the current cursor position.
  • mouse_click: Performs a mouse click (left/right/middle, double).
  • mouse_move: Moves the mouse to specified coordinates.
  • get_screen_size: Gets the screen dimensions.

Prerequisites

  • OS: Windows (PowerShell 7+ recommended, but 5.1 works)
  • Application: Telegram Desktop installed and logged in.
  • Node.js: (>=14.x)

Project Structure

  • scripts/: Contains the PowerShell automation scripts.
  • .tmp/: Stores temporary files, primarily verification screenshots.
  • server.js: Main MCP server implementation.

MCP Agent Instructions

  1. Always use Base64 for message content if it contains anything other than simple English ASCII. This guarantees that emojis and Russian text are transmitted correctly.
  2. Check the Exit Code: If the script returns 0, it ran successfully.
  3. Verify via Screenshot: The scripts output the path to a screenshot (e.g., .tmp/2025...capture.png). Read this file or listing the directory to confirm the visual state if needed.

License

MIT

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About Dev Tools

How do I install Dev Tools?

Run npx mcp-server-dev-tools, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Dev Tools safe to use with an AI agent?

Its trust score is 49 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Dev Tools still maintained?

The last commit was 8 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.