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.Claude Desktop
An extension Claude Desktop installs
Claude Code
Its own
claude mcp add, user scopeCursor
Cursor’s install link
VS Code
VS Code’s install link
VS Code Insiders
The nightly build, set up separately
Codex
One file the CLI, IDE and ChatGPT app share
LM Studio
One entry in its
mcp.jsonKiro
Kiro’s install link
Cherry Studio
Cherry Studio’s install link
Cline
The settings file every Cline surface shares
AnythingLLM
One entry in its server file
Gemini CLI
Its own
mcp add, user scopeGitHub Copilot CLI
Its own
mcp addOpenCode
Its own
mcp add, terminal and desktopSet 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.Raycast
Three values for its Install MCP Server form
ChatWise
Import JSON from Clipboard
goose
A YAML block for
config.yamlWindsurf
JSON for
mcp_config.jsonWarp
JSON for
.mcp.jsonZed
A
context_servers blockPerplexity
Two values for its Add Connector form
JetBrains AI Assistant
JSON for every JetBrains IDE at once
BoltAI
JSON for its plugin settings
Msty Studio
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:What Set up never does
It writes
- One
pomeroyentry, 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
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.Why cloud assistants cannot connect
What runs where, and the desktop equivalents that work today.