Log inSubmit server
Macuse logo

Macuse

Controls native macOS apps and any Mac GUI through local MCP tools for calendars, messages, files, automation, and more.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Macuse

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for macuse, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

The macuse MCP server connects AI clients to native macOS apps and provides computer-use controls for graphical interfaces. It runs locally through the Macuse app, exposing MCP tools over the app's built-in command and handling authorization, permissions, and reconnection. Use it to work with Calendar, Mail, Notes, Reminders, Messages, Contacts, Maps, Shortcuts, Stickies, or apps without dedicated integrations. macOS 13 or later is required, and write actions in Codex currently fail because Codex declines third-party consent prompts.

Use cases

  • Schedule and update calendar events
  • Search and organize native Mail, Notes, and Reminders data
  • Read and send Messages conversations
  • Run installed macOS Shortcuts
  • Operate Mac apps without dedicated integrations

Key features

  • Native macOS app access
  • Computer use for graphical Mac apps
  • Local MCP connectivity
  • Per-client and per-app permissions
  • Maps, location, and Shortcuts support
  • Claude Code and Codex plugin skills

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

4/4 checks healthy over the last 35d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars45Stargazers on the source repository.
Last commit2mo agoMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Macuse works

What the macuse MCP server does

The macuse MCP server gives MCP-compatible AI clients access to native macOS functionality through the Macuse application. It supports reading and writing data in Calendar, Mail, Notes, Reminders, Messages, Stickies, and Contacts. It also exposes place search, directions, travel-time and location features through Maps, plus the ability to browse and run installed Shortcuts with optional input.

A separate computer-use capability lets an agent inspect and operate graphical Mac applications that do not have a dedicated integration. Supported actions include clicking controls, entering text, navigating menus, completing web forms, and operating enterprise software. Work can run in the background while the user's active window and cursor remain undisturbed.

How it works

The macuse MCP server is backed by the macuse mcp command included in the Macuse macOS app. The app performs MCP protocol handling, client authorization, permission management, and reconnection locally.

Clients receive separate authorization through Macuse. Permissions are managed per client and per app, and sensitive applications may require confirmation for every access. Revoking a client's authorization also removes its app permissions.

Setup and configuration

Install Macuse from the product download page, place Macuse.app in /Applications, launch it, and grant the requested macOS permissions. Then choose the connection method for the client:

  • Claude Desktop uses the released macuse.mcpb bundle. Double-clicking the bundle adds it to Claude Desktop.
  • Claude Code and Codex can use the agent plugin, which adds MCP tools and workflow skills.
  • Other clients that accept a custom command can launch /Applications/Macuse.app/Contents/MacOS/macuse with the mcp argument.

Set MACUSE_BINARY when the application is installed somewhere other than the default path. The .mcpb route requires Node 20.8.1 or newer, although Claude Desktop supplies the bundled runtime. The agent plugin does not require Node.

The minimum supported operating system is macOS 13 Ventura, on either Apple Silicon or Intel. The first tool call requires approval of the authorization prompt in the Macuse window.

Tools and capabilities

The available functionality covers:

  • Calendar event creation, search, scheduling, and free-time discovery
  • Mail search, message organization, and draft creation
  • Note search, capture, and appending content
  • Reminder creation with due dates and priorities, completion, and list search
  • Message reading, sending, and conversation search
  • Sticky-note search, reading, and creation
  • Contact lookup by name, email, phone number, or company
  • Maps place search, directions, travel time, and current location
  • Shortcut discovery and execution
  • GUI inspection and interaction across Mac applications

The plugin also includes skills for setup, native-app workflows, and computer-use operation.

Limitations and notes

Codex can read through the integration, but write operations currently fail because it automatically declines consent prompts from third-party MCP servers. Claude Desktop needs the bundle because it does not directly accept remote HTTP connectors. The repository's MIT license applies to the MCP bundle; the Macuse macOS application is a separate commercial product.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Macuse

macuse is an MCP server that connects AI clients to native macOS apps and graphical Mac interfaces. Its main tools work with Calendar, Mail, Notes, Reminders, Messages, Contacts, Maps, Stickies, and Shortcuts, while computer-use actions click, type, navigate menus, and operate unsupported applications locally.

Install Macuse.app in `/Applications`, launch it, grant its requested permissions, and connect through the client-specific method. Claude Desktop uses the `macuse.mcpb` bundle; Claude Code and Codex use the agent plugin; other clients can launch the `macuse mcp` command directly.

Yes, macuse works with Cursor through a custom MCP command. Configure Cursor to launch `/Applications/Macuse.app/Contents/MacOS/macuse` with `mcp` as its argument, or set `MACUSE_BINARY` if the app is installed in another location.

The macuse MCP server requires macOS 13 Ventura or later and supports both Apple Silicon and Intel Macs. The Macuse macOS app must also be installed and launched before the client connects.

No, Codex write operations currently fail because Codex automatically declines consent prompts from third-party MCP servers. Read operations work normally, and the repository provides a Codex agent plugin for connecting the tools.

Related MCP servers

All in OS Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMacuse AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/macuse?style=directory)](https://allmcps.com/mcp/macuse)
HTML Embed
<a href="https://allmcps.com/mcp/macuse"><img src="https://allmcps.com/api/badge/macuse?style=directory" alt="Macuse on AllMCPs" /></a>