> ## Documentation Index
> Fetch the complete documentation index at: https://pomeroy.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# AI assistants
> The 24 AI assistants Pomeroy sets itself up in, what setup does in each, and what to do when yours is not on the list.
Pomeroy works with any AI assistant that speaks MCP and runs on your Mac. It
knows twenty-four of them by name: it finds them, sets itself up in them, and
tells you what each one needs afterwards.
Every assistant reaches the same server and obeys the same switches. Connecting
a second one adds tools, not permissions.
## Set up in one click
Pomeroy uses whichever mechanism the vendor documents: an extension, an install
link, the assistant's own CLI, or its configuration file. You press **Set up**
and answer whatever prompt the assistant itself shows.
An extension Claude Desktop installs
Its own `claude mcp add`, user scope
Cursor's install link
VS Code's install link
The nightly build, set up separately
One file the CLI, IDE and ChatGPT app share
One entry in its `mcp.json`
Kiro's install link
Cherry Studio's install link
The settings file every Cline surface shares
One entry in its server file
Its own `mcp add`, user scope
Its own `mcp add`
Its own `mcp add`, terminal and desktop
## Set up by pasting
These have no configuration file Pomeroy can safely write, or no install link
their vendor documents. Pomeroy puts the exact configuration on your clipboard
and says where it goes.
Three values for its Install MCP Server form
Import JSON from Clipboard
A YAML block for `config.yaml`
JSON for `mcp_config.json`
JSON for `.mcp.json`
A `context_servers` block
Two values for its Add Connector form
JSON for every JetBrains IDE at once
JSON for its plugin settings
Two values for its Toolbox
## Mine is not on the list
Any assistant that can start a local MCP server works, from the same
configuration. Point it at the pipe:
```json theme={null}
{
"mcpServers": {
"pomeroy": {
"command": "/Applications/Pomeroy.app/Contents/MacOS/pomeroy-mcp"
}
}
}
```
If it takes a URL rather than a command, switch on the local address in
Pomeroy's **Connections** pane and give it [the
endpoint](/docs/configuration/http-endpoint) instead.
Pomeroy's **Copy configuration** button produces the same text.
## What Set up never does
**It writes**
* One `pomeroy` entry, in the file that assistant reads
* Nothing outside that entry
* The same bytes every time, so pressing **Set up** twice is safe
**It does not**
* Remove or rewrite another server in the file
* Rewrite a file that allows comments. Those go to your clipboard instead
* Change anything about the assistant beyond its server list
## After setup
| Assistant | What it needs |
| ------------------------------------------------------------------- | ------------------------------------------------- |
| Claude Desktop, Codex | A full quit and reopen |
| Claude Code, Gemini CLI, goose | A new session |
| Cursor, Cherry Studio, OpenCode, Warp, Zed, Perplexity, Msty Studio | Usually nothing; restart if the tools are missing |
| The rest | Nothing. They pick it up on their own |
## Cloud assistants
claude.ai in a browser, ChatGPT on the web and Grok cannot reach Pomeroy at all,
and that is a decision rather than a gap.
What runs where, and the desktop equivalents that work today.