MCP · Hosted chat and API

Connect FishOut to Grok (Custom MCP Connector)

Grok already searches X live. What FishOut brings it is triage: the X posts it collected once a day, read against your Brief, and Reddit, Hacker News, Bluesky, GitHub, the press and the rest — the conversations Grok cannot see from where it sits.

Setup steps checked against Grok's own documentation on 20 October 2026.

[01] CONNECT IT/ SETUP

Add FishOut to Grok

https://mcp.fishout.ai/mcp, on every plan.
1

Grok app — add a custom connector

Go to grok.com/connectors, choose New Connector, then Custom, and enter the server URL. On Business and Enterprise, a team admin provisions the connector in the console first.

server url

https://mcp.fishout.ai/mcp
2

Complete the sign-in

xAI’s page says only to “complete any required authentication” and does not describe the custom-connector sign-in further. FishOut answers with a standard OAuth challenge: sign in, pick the organization and projects, approve.

3

xAI API — a remote MCP tool

In the Responses API, add a tool of type mcp. allowed_tools keeps every other tool out of context; authorization is sent as the Authorization header, which is where a FishOut API key goes for a server-side job.

POST https://api.x.ai/v1/responses — tools[]

{
  "type": "mcp",
  "server_url": "https://mcp.fishout.ai/mcp",
  "server_label": "fishout",
  "allowed_tools": ["list_mentions", "get_mention"],
  "authorization": "Bearer <FISHOUT_API_KEY>"
}

Check it worked. In the app, ask Grok what the FishOut connector can do. Through the API, a response that lists an mcp_call to list_mentions means the tool reached FishOut.

[02] WORTH KNOWING FIRST/ LIMITS

Before it bites

Stated before you hit them.

FishOut checks X once a day and reads a very busy term only in part. For what is happening on X this hour, Grok’s own search is fresher.

In the native Python SDK the fields are allowed_tool_names and extra_headers, not allowed_tools and headers. The REST names above are the API’s.

Leave allowed_tools out and every one of FishOut’s 115 tools is loaded into context on each request.

xAI’s Responses API does not support require_approval for MCP tools, so a server-side job should be given only read tools.

Not tested by us yet. These steps follow xAI’s documentation, read on 20 October 2026.

[03] WHAT IT LOOKS LIKE/ GROK

A question in Grok

Invented brands; a real call.
Grok · webfishout · mcp
People on X are arguing about our pricing. Is the same thing happening anywhere else?
list_mentionsread-only
{
  "filter": {
    "query": "pricing",
    "from": "2026-10-13T00:00:00Z",
    "platforms": [
      "reddit",
      "hackernews",
      "bluesky"
    ]
  },
  "limit": 10
}
86
r/SaaSmeadowstack1d

Their new per-seat price makes no sense for a team of three

Reply, carefullyComplaint
70
Hacker Newsdriftwood_eng2d

Per-seat is fine if the free tier stays — does it?

Reply nowQuestion

From my X search: about forty posts, mostly about seat minimums. From FishOut: the same complaint on r/SaaS, and an HN question about whether the free tier stays — that one has a clear answer and is worth replying to.

[04] WATCH ANY PLATFORM/ SAME SERVER
[05] WHERE YOU APPROVE IT/ SETTINGS

Connections live in FishOut

Revoke Grok under Settings → API & MCP; it stops at the next call.
API & MCP · connected clients2 connected

You — Grok

readseen just now

66

calls / 7d

Devon — Windsurf

read · writeseen 15h ago

46

calls / 7d

Questions

Sources