Skip to content

Grok opsera Prompt/search_opsera

How to: Grok opsera search_opsera

client:Grok transport:sse prompt:search_opsera

Add opsera to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "opsera": {
      "type": "sse",
      "url": "https://agent.opsera.io/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    search_opsera is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Grok will not call it for you.

  3. 04

    If it does not appear, check that opsera 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 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.