Skip to main content

Page fetching

Page fetching. In your CLI, over MCP, your way.

Turn a URL into readable text, including pages that need a browser. Connected once, it answers your terminal and every assistant you already use, under one permission.

For the agenda PDF, the council minutes, the pricing page that renders in JavaScript. One command in, text out, on the same record as everything else.

A real command line for page fetching

Not a chat window pretending. Every argument is a flag, output is text a pipe can read, and each call lands on your record with the daily ceiling watching.

Connect the account once, in the browser, and the terminal has it from then on. No key on your laptop, nothing in your shell history worth stealing.

Page fetching from the command line

brad@macbook · gbrainio
gbrainio auth grant firecrawlOpening https://gbrain.io/workspace/account/connections/firecrawlFinish in the browser, then your page fetching tools are live.gbrainio tool firecrawl search -hgbrainio tool firecrawl search <query>  Search the web (Firecrawl)  Search the web via Firecrawl. Returns titles, URLs, and descriptions.  Metered on this account; every call is recorded.  <query>  The search query  FLAGS    --limit <value>    Over MCP this tool is firecrawl_search.
Their consent screen, once. The credential never touches the laptop.

Or hand it to the assistant you already use

Claude Code, Cursor and Codex all speak MCP. Point any of them at one endpoint and they get the same page fetching tools, on the same permission and the same record as your terminal.

Page fetching over MCP, tool by tool

claude mcp add gbrain https://gbrain.io/mcp --header "Authorization: Bearer <token>"

Your assistant gets firecrawl_search and firecrawl_scrape. The token comes from the client's own page in the workspace, minted once and shown once.

Connect it once, use it everywhere

Their consent screen, one click, and one connection answers all of these. No key is pasted anywhere, and nothing runs before you allow it.