Skip to content
Edith

MCP server for Mac

An MCP server for your Mac

Edith ships an MCP server inside the app. Register it once with Claude Code, Codex, Cursor or VS Code, and the commands of every extension you enable become tools your agent can call, with the same safety rules as the command line.

What is MCP

One protocol, any agent.

MCP, the Model Context Protocol, is an open standard for connecting AI apps to tools. A server describes the tools it offers, and a client such as Claude Code decides when to call them.

Edith's server is ed mcp, the command line inside the app. Each command becomes one tool named after it: ed usage limits is edith_usage_limits and ed machines ls is edith_machines_ls. A tool takes an arguments array with exactly what the command accepts, and returns the same JSON as --json.

Server name
edith
Command
/Applications/Edith.app/Contents/MacOS/ed
Arguments
mcp
Transport
stdio
Protocol versions
2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05

Install

Add it to your client.

Every tab registers the same server. Use Edith's one-step installer, the client's own command, or edit the settings file.

One step with Edith

Adds an edith entry for Claude Code, backs up an existing settings file first and keeps every other server.

With the Claude Code command

Registers the same server through Claude Code itself.

Or edit the file yourself

Add this to ~/.claude.json. Edith adds a user-scope entry, so the tools are there in every project. Claude Code rewrites this file often, so prefer either command over editing it by hand.

{
  "mcpServers": {
    "edith": {
      "args": [
        "mcp"
      ],
      "command": "/Applications/Edith.app/Contents/MacOS/ed",
      "env": {},
      "type": "stdio"
    }
  }
}

Restart Claude Code, then ask it to call edith_catalog.

Prefer buttons? Settings, then Tools, lists each client as Connected or Not connected, and Connect all registers every client it finds on this Mac. ed mcp status prints the same report.

Previews and confirm

Destructive changes wait for you.

A command that needs --yes on the command line returns a preview over MCP until the call passes confirm. An agent that forgets gets the preview, never the change.

  1. 1

    Discover

    The agent calls edith_catalog. It lists every extension as enabled, installed or available, with its summary and example commands.

  2. 2

    Call

    It calls the matching tool. ed usage limits --refresh becomes edith_usage_limits with {"arguments": ["--refresh"]}.

  3. 3

    Install when needed

    If the extension is only available, the agent asks you, then calls edith_extensions_install with confirm. The server tells the client its tool list changed.

  • A call that slips --yes into its arguments is refused.
  • Installing, updating, enabling, disabling and removing extensions follow the same rule.
agent  edith_clipboard_clear {"arguments": ["--keep-pinned"]}
edith  preview: the entry ids that would go, nothing removed
agent  asks you, and you say yes
agent  edith_clipboard_clear {"arguments": ["--keep-pinned"], "confirm": true}
edith  applied: the same JSON as ed clipboard clear --json

Tools

Tool prefixes by extension.

Every command an extension adds becomes tools that start with its prefix. Open an extension to see its commands.

ExtensionTools
Audio Mixeredith_audio_*
Presenteredith_presenter_*
Color Pickeredith_color_*
Menu Bar Statsedith_system_*
Emoji Pickeredith_emoji_*
Homebrewedith_brew_*
Calendaredith_calendar_*
Jevedith_jev_*
Running Appsedith_apps_*
Keyboard Cleanedith_keyboard_*
Cleaneredith_cleaner_*
App Updatesedith_maintenance_*
Pluginsedith_skills_*
Shelfedith_shelf_*
Clipboardedith_clipboard_*
Musicedith_music_*
Docsedith_docs_*
LaTeXedith_latex_*
Memoryedith_companion_*
Studioedith_studio_*
Usageedith_usage_*
Launcheredith_bifrost_*
Lid Awakeedith_lid_awake_*
Attentionedith_attention_*
Machinesedith_machines_*
Downloadsedith_download_*
Site Auditedith_seo_*
Virtual Cameraedith_camera_*
Code Statsedith_code_stats_*
Agentsedith_herdr_*
Code Reviewedith_quinjet_*
Databaseedith_database_*

Built into the server

  • edith_catalog Every extension, its status, summary and examples.
  • edith_extensions_* Install, update, enable, disable and remove extensions.
  • edith_app_* Open pages, reveal settings and read app information.
  • edith_config_* Read and change Edith settings.
  • edith_permissions_* See and request the macOS permissions Edith uses.

While Jev is enabled with a TypeSafe key saved, the server also lists edith_find, which takes a plain-language request and returns the likeliest tools.

Examples

Ask in plain words.

Four prompts and the tools an agent calls to answer them.

“How much of my Claude limit is left, and what did I spend this week?”

edith_usage_limits {"arguments": ["--refresh"]}
edith_usage_summary {"arguments": ["--range", "week"]}

Uses Usage.

“Merge intro.pdf, body.pdf and appendix.pdf into one PDF.”

edith_catalog {"query": "pdf"}
edith_extensions_install {"arguments": ["studio"], "confirm": true}
edith_studio_run {"arguments": ["pdf.merge", "intro.pdf", "body.pdf", "appendix.pdf"]}

Uses Studio.

“Which containers are stopped on my build server?”

edith_machines_ls {}
edith_machines_docker_ps {"arguments": ["--all", "build-box"]}

Uses Machines.

“Clear my clipboard history, but keep what I pinned.”

edith_clipboard_clear {"arguments": ["--keep-pinned"]}
edith_clipboard_clear {"arguments": ["--keep-pinned"], "confirm": true}

Uses Clipboard.

Frequently asked questions

Where does the Edith MCP server run?

On your Mac. Your client starts /Applications/Edith.app/Contents/MacOS/ed mcp as a local process and talks to it over standard input and output. Each tool call runs the matching ed command and returns its JSON.

Do I need the ed command on my PATH?

No. Every registration points at the ed inside the app, so it keeps working whether or not you ran ed install. To run the installer without it, use the full path: /Applications/Edith.app/Contents/MacOS/ed mcp install --client all.

Which tools will my agent see?

Tools exist only for extensions you have enabled, plus the built-in ones such as edith_catalog. When you install or enable an extension, the server sends notifications/tools/list_changed so the client lists tools again.

Can an agent delete something without asking?

Not through a destructive command. Those return a preview, and the server adds --yes only when the call passes confirm: true. Other commands run as soon as they are called, so your client's own tool approval still applies to them.

Does it work with other MCP clients?

Any client that can start a stdio server can use it. Point it at /Applications/Edith.app/Contents/MacOS/ed with the single argument mcp.

How do I remove it?

Run ed mcp uninstall --client all, or a single client name, or press Disconnect in Settings, then Tools. Only the edith entry is removed.

Get Edith.

From $35 once. No subscription. No account.

Download for macOS

Needs a license key · macOS 14 or later on Apple silicon · 6.4 MB