Grok Civic Prompt/regulatory_landscape
How to: Grok Civic regulatory_landscape
Add Civic to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"civic": {
"type": "http",
"url": "https://gateway.pipeworx.io/civic/mcp"
}
}
}-
02
Save the file and restart Grok.
-
03
regulatory_landscape 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 Civic 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
Same prompt, other clients
Read from the server itself, by connecting to it and calling prompts/list on 25 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.