Grok Parsley - Buyer Intent Signals Prompt/morning_briefing
How to: Grok Parsley - Buyer Intent Signals morning_briefing
Add Parsley - Buyer Intent Signals to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"parsley-mcp": {
"type": "http",
"url": "https://www.parsley.id/api/mcp"
}
}
}-
02
Save the file and restart Grok.
-
03
morning_briefing is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Grok 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.
Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs
Set these first
Parsley - Buyer Intent Signals will not start until these are set, so it never reaches Grok.
-
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.