NEWGive every one of your Grok Bots its own app database →

App data for your agent stack.

The data your agents produce, in a database people can read, filter, and share. No schema, SQL, or setup required.

USE HUTCH TO

  1. Run repeatable playbooksKeep instructions, files, owners, and current status together.
  2. Store and share team dataKeep research, customer records, product data, and files where everyone can find and update them.
  3. Hand work between agentsOne agent collects, another processes, and the team can see the result throughout.

Connect over MCP and say “save to Hutch.” Collections and views appear automatically.

Hutch demoLOOP

Teams + agents on the same page.

People review, organize, and update the work in visual views. Your AI reads and writes the same records from inside the chat apps you already use. No copy-paste handoffs, stale context, or work trapped in a chat.

PEOPLE / AGENTS / SHARED
WHO.01 — FOR PEOPLE

See and steer the work

Review records, change statuses, attach files, and organize collections as tables, boards, calendars, timelines, or galleries.

WHO.02 — FOR AI AGENTS

Pick up and continue the work

Claude, ChatGPT, and other AI apps can look up what’s there, add records, and update the work as they go.

WHO.03 — FOR EVERYONE

Leave it better for whoever is next

A decision, corrected record, or improved process becomes available to the next teammate or agent immediately.

The work stops living in separate chats

A useful answer in one person’s chat should become something the whole team can use. Save the result, the source data, or the improved process to Hutch, and every teammate and agent starts from the latest version next time.

READ / WRITE / SHARED
H
READ.001Your whole teamhumans, via web views
READ.002All their AI appsClaude, ChatGPT, and more
READ.003Every runtoday, next week, next quarter
ONE.01

Across your team

Shared collections, orgs, and magic-link invites. What Maria saved from ChatGPT on Wednesday, you can pull into Claude on Thursday, with no copy-paste relay between people.

ONE.02

Across humans and agents

The same collection is a kanban board to a person and a lookup for your AI. Both read it, both write it, and neither side works from a stale copy.

ONE.03

Across runs

Chats end. Collections don’t. Caught a missing step this run? Add it to the checklist, and every future run includes it, whether a person picks it up or an AI does.

You see a board. Your AI sees the same records.

Every collection becomes a table, kanban, calendar, timeline, or gallery. Your AI reads and updates the same collection from the chat, so it does the work while you review, edit, and steer.

05 VIEW TYPES
save these subject lines to hutch as drafts
Saved 6 records to Newsletter drafts.
newsletter-template.md attached
Table01
Kanban02
Calendar03
Timeline04
Gallery05
Todos
> "save anything we call out as a todo to hutch"A shared to-do list your whole team can see and update between chats.
Screenshot of the Todos collection in Hutch
Help center updates
> "as we change the product, save any help-center page that needs a rewrite to hutch"A checklist of pages to update that the team works through together.
Screenshot of the Help center updates collection in Hutch
Customer feedback
> "as customers write in, save feature requests and complaints to hutch"A board of feedback sorted by product area that everyone works from.
Screenshot of the Customer feedback collection in Hutch
Support issues
> "go through this week’s support emails and save every recurring issue to hutch"A calendar of customer issues as they show up, so you see patterns instead of one-off tickets.
Screenshot of the Support issues collection in Hutch

Use Hutch from

Hutch connects from your AI app’s settings. Everyone on the team connects their own; one shared collection sits behind all of them.

09 SUPPORTED

Using a coding agent like Claude Code, Codex, or Hermes? Paste this in and it sets itself up.

PROMPT
Connect Hutch (hutchdb.com) to this agent as an MCP server.

- URL: https://app.hutchdb.com/api/mcp
- Transport: remote streamable HTTP
- Auth: OAuth (no API key). I'll approve in the browser.

1. Add the server for my user account, not just this project, so it works everywhere.
2. Start the OAuth login, or tell me exactly what to click if you can't start it yourself.
3. Tell me if I need to restart or reload you. Then call hutch_list_collections to confirm it works.

Before you ask

FAQ.01

Do my teammates need to be technical?

No. People use Hutch in the browser: kanbans, calendars, tables. Only the agents speak MCP, and connecting one is a settings change in your AI app, not a code change.

FAQ.02

Which AI does Hutch use?

Yours. Hutch has no bundled assistant and no AI credits to meter. It’s the shared workspace for the agents your team already uses and already pays for: Claude, ChatGPT, Codex, whatever ships next.

FAQ.03

How do agents connect?

Hutch is an MCP server. OAuth-capable clients such as Claude and ChatGPT connect from their settings with a sign-in flow. Runtimes that do not support interactive OAuth, including OpenClaw, connect with a Hutch API token.

FAQ.04

What exactly is a collection?

A shared set of records and files: your customer personas are one, this week’s newsletter run is another. Agents create them automatically the first time they save; people see each one as a table, kanban, calendar, timeline, or gallery.

FAQ.05

Is my data locked in?

No. It’s Postgres underneath, the core is open source (AGPL), and everything is reachable over plain MCP and REST. Export it, or move to self-hosting whenever you like.

FAQ.06

What does it cost?

Self-hosting the open-source core is free, forever. Hosted plans are on the pricing page.

Create your shared AI workspace

Start with one playbook, reference library, or active project. Self-host the open-source core, or sign up and let us run it.