Deskwright vs Applescript MCP

A side-by-side look at the Deskwright and Applescript MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Deskwright logoDeskwrightOS Automation · Local subprocess (stdio)Agents use real GNOME/Wayland apps: on your screen, or an invisible second desktop you never see43FairAuth: not declaredApplescript MCP logoApplescript MCPOS Automation · Local subprocess (stdio)MCP server that execute applescript giving you full control of your Mac44FairAuth: not declared

Verdict: choose Deskwright for os automation work as a local process; choose Applescript MCP for os automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Deskwright logoChoose Deskwright when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
Explore Deskwright

Applescript MCP logoChoose Applescript MCP when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
Explore Applescript MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDeskwright logoDeskwrightApplescript MCP logoApplescript MCP
CategoryOS AutomationOS Automation
Quality signal43/100 · Fair44/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars10465
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Deskwright tools

No tool names declared yet. Check the project README from the listing page.

Applescript MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Deskwright

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "deskwright": {
      "command": "uvx",
      "args": [
        "deskwright"
      ]
    }
  }
}

Applescript MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "peakmojo-applescript-mcp": {
      "command": "npx",
      "args": [
        "@peakmojo/applescript-mcp"
      ]
    }
  }
}

Frequently asked questions

Deskwright is categorized under OS Automation and uses a local stdio subprocess. Applescript MCP belongs to OS Automation and uses a local stdio subprocess. Pick Deskwright for os automation work and Applescript MCP for os automation.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Deskwright has no declared pricing — check the project's own site. Applescript MCP is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add deskwright and peakmojo-applescript-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Deskwright has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 10 GitHub stars. Applescript MCP has 44/100 (Fair) with 2 views, 0 installs and 465 GitHub stars.