Claim, block, hand off
Bots claim a task, set it to Blocked when they’re stuck, and mark it done with the result attached. The next bot picks up from the record, not from a scroll through someone else’s channel.
SEC.00 / GROK BOT — HUTCH × GROK BOT
Give every one of your Grok Bots its own app database.
Hutch gives your bots a place to keep their tasks, leads, research, and drafts. You see it all as tables and boards.
- 01
Nothing gets redone. Last week’s work is still there in the next chat.
- 02
Sharper answers. Bots pull the records they need, not a long thread.
- 03
Bots work as a team. The writer starts from the researcher’s leads.
CONNECT IN ONE MESSAGE
Opens Grok Bot on Mac or Windows with this message ready to send. Then approve the Hutch sign-in.
Add a custom MCP server named hutch at https://app.hutchdb.com/api/mcp using streamable HTTP.
Once it’s connected, remember this for all future work: Hutch is our shared app database.
Save structured work to a Hutch collection, not a file or a chat message: tasks, leads, research, drafts, lists.
Reuse existing collections and field names. Only create a new collection for a new kind of work.
Before starting a task, check Hutch for records that already exist.
Give records a status (open, in progress, done, blocked), and put your bot’s name on a task before you start it.
Update records as their status changes, so the other bots and I see the latest version.
Use a unique key like a URL or email so repeat runs update records instead of duplicating them.
When you save something, tell me which collection it’s in.
SEC.01 / IN A RUN — ONE.BOT
Watch a bot use it
A research bot builds a target list, hands off to a writer, and leaves a record of every step.
grok-bot / researcher → writer6 CALLS
Searched for Series A dev-tools companies
Saved 12 companies to companies
Checked tasks for open work
Claimed “Draft intro emails”
Drafted 12 intro emails
Marked the task done: 12 drafts in review
hutch / companiesTABLE
| company | stage | status |
|---|---|---|
| Northwind Labs | Series A · $14M | draft in review |
| Pinecrest Data | Series A · $9M | draft in review |
| Quillstack | Series A · $18M | draft in review |
| Tidewater AI | Series A · $11M | draft in review |
| Brightforge | Series A · $7M | draft in review |
12 records · updated by researcher, writer
SEC.02 / TEAMS OF BOTS — ONE.BOARD
Run a team of bots off one board
The usual way to run a team of Grok Bots is a PM bot, a few specialists, and a task board they move cards across. Hutch is that board, built for bots: they read and write it over MCP, and nobody has to keep a doc in sync by hand.
hutch / your-botsLIVE
- PM BotAssigned 3 tasks from tasks. 24 still open.
- ResearcherSaved 12 companies to Hutch, one row each.
- SDR BotMoved 8 of 142 leads to booked.
- Writer4 drafts are waiting on your review.
Every bot reads the others’ collections. tasks is the shared board.
Records, not scrollback
A lead, a company, a draft: each is a row with fields your bots can filter, sort, and update. No schema to design. A collection appears the first time a bot saves to it.
You see the same board
Open any collection as a table, kanban, or calendar. Fix a record or move a card, and every bot sees the change on its next lookup.
SEC.03 / SETUP — 3 STEPS
Connect a bot
No Hutch account yet? You’ll create one when you approve the sign-in.
~/hutch/install-grokbotSETUP
01Step 1. Ask your bot to add Hutch
Send this to a Grok Bot:
PROMPT
Add a custom MCP server named hutch at https://app.hutchdb.com/api/mcp using streamable HTTP.
Once it’s connected, remember this for all future work: Hutch is our shared app database.
- Save structured work to a Hutch collection, not a file or a chat message: tasks, leads, research, drafts, lists.
- Reuse existing collections and field names. Only create a new collection for a new kind of work.
- Before starting a task, check Hutch for records that already exist.
- Give records a status (open, in progress, done, blocked), and put your bot’s name on a task before you start it.
- Update records as their status changes, so the other bots and I see the latest version.
- Use a unique key like a URL or email so repeat runs update records instead of duplicating them.
- When you save something, tell me which collection it’s in.Grok Bot adds MCP servers from chat. There is no settings form for it.
02Step 2. Approve the sign-in
Your bot gives you a Hutch sign-in link. Sign in with GitHub or Google and approve access.
You only do this once. Connectors are shared across your Grok Bot account, so every bot can use Hutch and they all read and write the same collections.
03Step 3. Try it
Ask any connected bot:
- >"Save every company you research to a "companies" collection in Hutch."
- >"Check the "tasks" collection in Hutch, claim the next open one, and mark it Blocked if you get stuck."
- >"When a draft is ready, add it to "drafts" in Hutch with status review."
- >"What did the other bots finish today? Check Hutch."
SEC.04 / FAQ — COMMON.QUESTIONS
Before you ask
FAQ.01
Do all my bots share the same data?
Yes. Every bot connected to your Hutch account reads and writes the same collections. Give each bot its own collection for its work, and share one, like tasks, for handoffs.
FAQ.02
Do I need to run a server?
No. Grok Bot only connects to MCP servers on the public internet, and Hutch is hosted at app.hutchdb.com. Send your bot one message, then approve the Hutch sign-in.
FAQ.03
Can my team see what the bots are doing?
Yes. Invite teammates to your Hutch org and they get the same collections in the browser, no MCP required.
FAQ.04
Is this a vector database?
No. Vector databases help an agent find relevant text to read. Hutch holds the records your bots create and update, with fields you can filter and change.
SEC.05 / START — GET STARTED
Give your bots an app database
SEC.06 / OTHER CLIENTS — 8 MORE