cd /news/ai-tools/show-hn-statey-the-database-your-ai-… · home topics ai-tools article
[ARTICLE · art-41265] src=statey.ai ↗ pub= topic=ai-tools verified=true sentiment=· neutral

Show HN: Statey – the database your AI shares across every chat, over MCP

Scott launched Statey, a database without a UI that AI agents access via MCP tools, allowing users to store and retrieve structured data across chats in Claude, ChatGPT, and other LLMs without managing schemas. The product handles schema versioning and migrations automatically, and includes agent key management, multi-user support, and activity logs. Statey is available via MCP in Claude, Claude Code, and Cursor.

read2 min views1 publishedJun 26, 2026

Hey all - Scott here,

I was a heavy Linear user until I noticed I hadn't opened the UI in days. I was just asking Claude to pull up the tickets I cared about and draw whatever view I needed in the moment. At some point it clicked that I didn't need Linear, I needed the database underneath it. Then I realized it was the same for Confluence, Jira, and Pipedrive. But I didn't want to stand up Postgres and babysit schemas and migrations to get structured, collaborative data into Claude. I just wanted structured storage I could talk to and that followed me from Claude Desktop to Claude Code to Codex to ChatGPT. I wonder if you do to?

That's what Statey is: a database with no UI, used entirely through MCP tools. You don't design a schema up front. You just tell your LLM what you want to store and Statey creates the collection. If you change your mind later it versions the schema and handles the migration invisibly (additive changes apply immediately, breaking ones ask first and return a diff). All you concern yourself with is getting work done and improving your methods.

Also, while I was in there I built out agent key management, multi-user, full attribution and activity logs so we can always trace who changed what and why. What I haven’t built yet is the reactive part, triggers that fire an agent when data changes. I can find about 100 uses for it, so that’s coming soon.

One thing I'm genuinely unsure about and would also like feedback on is the security model. It's a store any connected MCP client can write to, so prompt injection and over-broad agent access might be concerns. Attribution and the event log let you see what an agent did after the fact, but the issue has already happened. If you've thought about this for agent-writable data, tell me where I'm wrong.

To try it: mcp add mcp.statey.ai in Claude, Claude Code, or Cursor, or get the connect steps at statey.ai. Happy to answer anything!

Thanks hackers!

Comments URL: [https://news.ycombinator.com/item?id=48691461](https://news.ycombinator.com/item?id=48691461)

Points: 2

── more in #ai-tools 4 stories · sorted by recency
── more on @statey 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/show-hn-statey-the-d…] indexed:0 read:2min 2026-06-26 ·