Macuse

io.github.macuse-appPublished by GitHub account macuse-appv1.3.0Updated Oct 24, 2026

MCP server for Mac — control Calendar, Mail, Notes, Reminders, and any Mac app, fully on-device.

VerifiedSTDIODesktop onlyProductivity & WorkflowBrowser AutomationCommunication & Collaboration

Overview

AI-generated overview

Macuse is a local macOS MCP server that lets an AI assistant read and write Apple apps like Calendar, Mail, Notes and Reminders, and drive any Mac app's GUI.

What you can do
Read and manage Calendar events, Mail messages, Notes, Reminders, Stickies and Contacts, including creating, searching and organizing items and drafting replies. Read and send iMessages and search conversations. Look up places, directions, travel time and current location, and browse or run installed Shortcuts. Control any Mac app through Computer Use: click elements, type text, navigate menus and fill in forms in the background. Install as an agent plugin for Claude Code and Codex to add setup and workflow skills.
When to use it
Useful when you want an assistant to act on your Mac's native apps and data rather than only answer questions, for example scheduling meetings, triaging mail, capturing notes and tasks, or automating apps that have no dedicated integration.
Requirements
macOS 13.0 (Ventura) or later on Apple Silicon or Intel, with the Macuse macOS app installed and launched. Node 20.8.1+ only for the Claude Desktop .mcpb bundle. The binary path can be overridden with the MACUSE_BINARY environment variable. OAuth approval is required on first tool call, and macOS per-app permissions must be granted.
Before you install
The assistant can write and send data: create events, send iMessages, draft and organize mail, and run Shortcuts. Computer Use can click and type in any app, including sensitive ones. Grant per-app permissions deliberately; password managers and banking apps re-confirm each time. Codex write operations currently fail because consent prompts are auto-declined. The free tier has daily limits; a paid Lifetime option exists.

Installation

In SourceWeft

  1. Open Macuse in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Macuse — AI Superpowers for Every Mac App

Give your AI direct control of Calendar, Mail, Notes, Reminders, Messages, and any other Mac app over the Model Context Protocol — an MCP server for Mac plus Computer Use for macOS, fully on-device.

Works with Claude Desktop, Cursor, Codex, Raycast, VS Code, Warp, Zed, LM Studio, Windsurf, and any MCP-compatible client.

This repo packages Macuse for agent clients: the Claude Desktop .mcpb installer and the agent plugin for Claude Code and Codex. The macOS app itself and the full docs live at macuse.app.

You useInstall thisGet
Claude Code, CodexAgent pluginMCP tools + skills
Claude Desktop.mcpb bundleMCP tools
Cursor, Raycast, VS Code, Zed, …Direct commandMCP tools

All three connect to the same local server. The plugin additionally installs skills — instructions that teach the agent how to use the tools correctly instead of discovering the parameter shapes by trial and error.

What Macuse Does

Two complementary ways for AI to work with your Mac. Everything runs locally — your data never leaves your device.

Native App Integrations

Your AI reads and writes directly to macOS apps through natural conversation.

ToolboxWhat you can ask
Calendar"Schedule a meeting next Tuesday at 3pm", find free time, manage events
Mail"Draft a reply to this email", search inbox, organize messages
Notes"Find notes mentioning the Q2 launch", capture ideas, append to notes
RemindersCreate tasks with due dates and priorities, mark complete, search across lists
MessagesRead and send iMessages, search conversations
StickiesSearch, read, and create sticky notes in Apple Stickies
ContactsLook up by name, email, phone, or company
Maps & LocationPlace search, directions, travel time, current location
ShortcutsBrowse installed Shortcuts and run them with optional input

Computer Use on macOS

See and control any Mac app — even ones without a dedicated integration. Macuse brings Computer Use to macOS for any MCP client, not just Claude or Codex.

  • Click any element, type text, navigate menus, drive any app
  • Fill out web forms, operate enterprise software, automate APIs that don't exist
  • Runs in the background — your cursor and active window stay untouched while AI works in another app

Install as an Agent Plugin

For Claude Code and Codex. Bundles the MCP server with three skills, so the agent knows the workflows, parameter formats, and permission-error recovery paths up front.

  1. Install Macuse: download from macuse.app/download, drag Macuse.app to /Applications, and launch it once

  2. Add the marketplace and install:

    Claude Code

    shell
    /plugin marketplace add macuse-app/macuse-mcp/plugin install macuse@macuse-plugins

    Codex

    shell
    codex plugin marketplace add macuse-app/macuse-mcpcodex plugin add macuse@macuse-plugins

  3. Approve OAuth: on the first tool call, approve the authorization prompt in the Macuse window

Restart the session (or run /reload-plugins in Claude Code) if tools do not appear immediately. Set MACUSE_BINARY if the app is not in /Applications.

Skills Included

SkillCovers
macuse-setupInstall, connect a client, grant macOS permissions, diagnose a broken setup
macuse-appsCalendar, Mail, Reminders, Notes, Messages, Location — routing, parameter shapes, workflow ordering
macuse-computer-useDriving any Mac app's GUI — inspect/act/verify loop, element targeting, error recovery

The agent loads a skill only when the task calls for it. Details live in plugins/macuse/README.md.

Codex users: write operations currently fail because Codex auto-declines consent prompts from third-party MCP servers (openai/codex#18896). Reads work normally.

Install for Claude Desktop

Claude Desktop doesn't support remote http:// connectors directly, so this .mcpb is the one-click installer. For other MCP clients, see Use With Other Clients below.

  1. Install Macuse:
    • Download from macuse.app/download
    • Drag Macuse.app to /Applications and launch it
    • Grant the permissions the app prompts for
  2. Install the bundle: download macuse.mcpb from Releases and double-click to open in Claude Desktop
  3. Approve OAuth: approve the authorization prompt that pops up — connection done

To uninstall, remove the entry from Claude Desktop settings.

Use With Other MCP Clients

For clients that accept a custom command (Cursor, Codex, Raycast, VS Code, Warp, Zed, LM Studio, Windsurf, ChatWise, and more), skip this bundle and configure directly:

json
{  "mcpServers": {    "macuse": {      "command": "/Applications/Macuse.app/Contents/MacOS/macuse",      "args": ["mcp"]    }  }}

Per-client setup guides: macuse.app/docs/clients.

Privacy & Permissions

  • Local-only. All processing stays on your Mac. No cloud, no telemetry of your content.
  • Per-app permissions. Allow, deny, or one-time-approve each AI client for each app it touches. Sensitive apps like password managers and banking re-confirm every time. Revoking an AI client automatically clears its app permissions.
  • Per-client OAuth. Each MCP client gets its own authorization, manageable in Macuse settings.

How This Works

Every install path is a thin shim over the same thing: macuse mcp, the CLI built into the Macuse macOS app. All MCP protocol handling, OAuth, permissions, and reconnection live inside the app.

  • The .mcpb bundle is a ~130 LOC Node stdio wrapper that spawns macuse mcp and forwards JSON-RPC over stdin/stdout. It exists solely because Claude Desktop doesn't yet support http:// remote connectors directly.
  • The plugin skips Node entirely — a shell launcher execs the same binary, and adds the skills on top.

Override the binary path with the MACUSE_BINARY environment variable (configurable in the Claude Desktop bundle UI). Default: /Applications/Macuse.app/Contents/MacOS/macuse.

Repo Layout

.claude-plugin/marketplace.json   Claude Code marketplace catalog.agents/plugins/marketplace.json  Codex marketplace catalogplugins/macuse/                   The plugin — manifests, launcher, skillssrc/, bin/                        Node stdio wrapper for the .mcpb bundlemanifest.json                     .mcpb bundle manifest (Claude Desktop)server.json                       MCP Registry entry

Both marketplaces point at plugins/macuse in this repo, so one push updates every channel. Version strings across package.json, manifest.json, and both plugin manifests are synced at release time by scripts/sync-manifest-version.js.

Validate plugin changes before pushing:

shell
claude plugin validate ./plugins/macuse --strict   # plugin manifestclaude plugin validate . --strict                  # marketplace catalog

Requirements

  • macOS 13.0 (Ventura) or later — Apple Silicon or Intel
  • Macuse macOS app installed
  • Node 20.8.1+ for the .mcpb bundle only (bundled by Claude Desktop's runtime); the plugin has no Node dependency

Links

License

This MCPB bundle is MIT-licensed. The Macuse macOS application is a separate commercial product — see macuse.app for details.

Source: README.md at commit a22e85d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.