Connect 24 AI assistants to your Mac - Pomeroy

Pomeroy

6 min read Original article ↗

Connect · Updated 9 September 2026

Connect Pomeroy to your AI assistant

One menu-bar app holds the macOS permissions and serves your Mac apps over MCP. Any assistant that can start a local MCP server can use it: some in one click, the rest by pasting a configuration Pomeroy writes for you.

Download for Mac

Free for 50 actions a week, shared across every assistant you connect. No account, no card.

Set up with one click

Each of these documents a way in: an extension, an install link, its own command, or a file it reads. Pomeroy uses that way, and the assistant’s own confirmation is the consent step.

Set up by pasting a configuration

These have no file Pomeroy can write, or a route nobody has checked on a Mac yet. Pomeroy puts the exact text on your clipboard and says where it goes. When a route is verified, the assistant moves up to one click.

Or connect to a local address

Everything above works by starting a small program on your Mac. Some assistants cannot do that: one running in a container, or one that takes a URL and nothing else. For those, Pomeroy has an address on this Mac. It is off until you switch it on, it answers only on this Mac, and Pomeroy writes it into the assistant’s own settings, so you do not type it.

You choose how it is guarded

One setting for the whole address, and each choice accepts one thing and refuses the others.

Token, the default
One secret for the address. Pomeroy writes it into every assistant it can reach, and you can read it for anything it cannot: a container, a script, a request made by hand.

Approval
No secret to hand around. The assistant asks for itself, you answer in a Pomeroy window, and it gets its own credential that you can revoke on its own.

Open
Nothing is checked. Anything running on this Mac can ask Pomeroy for your mail and messages. It exists because a container or a runner can genuinely need it, and switching to it asks you first.

Nothing on your network can reach the address, whichever you pick. Why, and what a tunnel does not buy.

What it looks like

The plainest form, for an assistant that takes a URL. Pomeroy fills in the address and, in Token mode, the header.

Add to your AI assistant's MCP settings
{
  "mcpServers": {
    "pomeroy": {
      "type": "http",
      "url": "http://127.0.0.1:13579/mcp"
    }
  }
}

Containers on Docker Desktop reach it, and so do dev containers. A virtual machine on its own subnet does not. When you need this.

Or start from the app

Each Mac app has its own page: what any assistant can and cannot do in it, and a link for every assistant and app pair.

Using something else?

Any assistant that runs a local MCP server takes this, the plainest form. Pomeroy’s Copy configuration button puts the same text on your clipboard.

Add to your AI assistant's MCP settings
{
  "mcpServers": {
    "pomeroy": {
      "command": "/Applications/Pomeroy.app/Contents/MacOS/pomeroy-mcp"
    }
  }
}

Not on this list

claude.ai and Cowork on the web, ChatGPT on the web, and Grok cannot use Pomeroy. They reach only servers on the public internet, and Pomeroy runs none, on purpose. Why that is a stance.

Connected right now

Pomeroy’s menu bar shows which assistants are connected right now, under the name each gives when it connects. The two ways in are guarded differently, and only one of them can ask you first. Which, and why.

Bring the assistant you already use.

Get 50 actions every week. No Pomeroy account or payment card required. Requires macOS 15 or later.

Download for Mac