Claude Desktop Parsley - Buyer Intent Signals Prompt/coaching_gaps
How to: Claude Desktop Parsley - Buyer Intent Signals coaching_gaps
Add Parsley - Buyer Intent Signals to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"parsley-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://www.parsley.id/api/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
coaching_gaps is surfaced in the attachment menu, under the server's name. Unlike a tool, you invoke it deliberately — Claude Desktop will not call it for you.
-
04
If it does not appear, check that Parsley - Buyer Intent Signals is connected and that you are looking at its prompts rather than its tools.
Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs
Set these first
Parsley - Buyer Intent Signals will not start until these are set, so it never reaches Claude Desktop.
-
PARSLEY_API_KEY
Same prompt, other clients
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.