A USB drive for your brain

Your context,
in every AI.

masst.ai is the context layer you own. Write who you are once, choose how deep each part goes, and every AI reads only the layers you allow.

masst.ai/@aditya3 AIs connected
Aditya's Root as a graph: fifteen Strands orbiting a gold centre, coloured by depth, from champagne public Strands to graphite private ones.Explore the live graph
Works withChatGPTClaudeGeminiCursorPerplexityAny MCP client

The problem

Every AI starts from zero. And every memory is locked in.

ChatGPT's memory doesn't reach Claude. Claude's doesn't reach your coding agent. Every new tool and every new app meets you as a stranger, so you re-explain the same things, every day.

47×
“I'm a senior engineer at HireStella…”
typed into ChatGPT
38×
“I'm working on a product called masst…”
typed into Claude
61×
“I prefer concise answers, no fluff…”
typed into Cursor

LinkedIn is for people. GitHub is for code. Nothing holds your context, for every AI, under your control. Until now.

How it works

Three steps. Then never again.

  1. Write it once

    Your work, skills, preferences and projects, in short sections called Strands. Start from a template, a résumé, or connect GitHub and Calendar. Every suggestion waits for your approval.

  2. Choose how deep it goes

    Public, link, team or private. Each Strand sits at one depth and you can move it anytime. Sensitive fields are encrypted in your browser.

  3. Every AI reads what you allow

    The extension adds your context to new chats in ChatGPT, Claude and Gemini. Or share one link, or connect any agent over MCP.

You stay in control

Visibility is depth.

Your Root is a cross-section of you. The top layer is what anyone can read. Each layer down is seen by fewer people, and the bottom layer is yours alone.

Sensitive fields like ID numbers and bank details are encrypted in your browser with a passphrase only you know. We can't read them.

layer 01 · 0 m · topsoil · open · any AI

Public

Anyone, and any AI you point at your link.

  • masst project6
  • Skills6
  • Interests5
  • Food4
layer 03 · −2 m · subsoil · shared · your team

Grove

Your team: the people you work with and their AI tools.

  • Work6
  • Network4
  • Learning4
layer 04 · −3 m · bedrock · sealed · only you

Private

Only you. Never sent to an AI, your public page or the extension.

  • Career goals4
  • Preferences5
  • Health & routine5
  • Family4
  • Finances4

For AI apps and agents

Personalize from the first message.

Your users already wrote down who they are. Read it with one call, or add masst as an MCP server. No onboarding quiz, no cold start, and the user decides what you can see.

  • MCP server: get_masst_context and get_masst_strand
  • REST: GET /api/pollen/@handle and /@handle/strand
  • Browser extension for ChatGPT, Claude and Gemini
  • Sign in with masst (early access): users grant your app deeper layers, and revoke them anytime.
Any MCP clientlive
{
  "mcpServers": {
    "masst": { "url": "https://masst.ai/api/mcp" }
  }
}
REST200 OK
GET https://masst.ai/api/pollen/@aditya/masst

{
  "strand": "masst",
  "name": "masst project",
  "owner": "@aditya",
  "visibility": "public",
  "fields": [{ "key": "stage", "value": "Private beta" }, …],
  "content": "Product vision and collaboration signals…"
}
call to know your user
1
call to know your user
onboarding questions
0
onboarding questions
depths, set by the user
4
depths, set by the user

For teams

Your company's context, in every teammate's AI.

A Grove turns what your people already wrote about their work into shared context that your team's AI tools can read.

  • One Grove for the companyOrg, teams and people, each with the Strands they choose to share at Grove depth.
  • Ask across everyone's context“Who owns security?” answered from your team's Roots, with no wiki to keep up to date.
  • People keep controlNothing private or link-only ever reaches the Grove. Admins manage members, not people's data.
HireStella brain 13 people · 3 teams
Who owns security?
Charlie Reyes owns platform security and on-call. Kumari Shah signs off on vendor reviews. Aditya Narayan shipped the row-level security policies.

Answered from 6 Roots · Grove and Public depths only · sample Grove

Why not built-in memory?

Your AI's memory belongs to your AI. masst belongs to you.

Built-in memory is useful, inside one product. masst is the neutral layer underneath all of them, so switching tools never means starting over.

  • Works in other AI tools

    masst.ai · ChatGPT, Claude, Gemini, any MCP client

    Built-in AI memory · Only inside that product

  • Different people and apps see different parts

    masst.ai · Four depths, set per Strand

    Built-in AI memory · No

  • Apps and agents can read it, with your permission

    masst.ai · MCP server and REST API

    Built-in AI memory · No

  • Sensitive fields encrypted with your own key

    masst.ai · Yes, in your browser

    Built-in AI memory · No

  • You can read, edit and export all of it

    masst.ai · Every field, as JSON, anytime

    Built-in AI memory · Partly

Pricing

Start free. Pay when masst is part of your day.

Free

For trying masst with the AI tools you already use.

$0 forever

  • 1 Root
  • 5 Strands
  • Shareable link
  • Browser extension
  • 100 AI reads a month
Get started

Pro

Most popular

For people who use AI all day, across tools.

$10 / month

  • Unlimited Strands
  • Unlimited AI reads
  • Connected Strands
  • Full analytics
  • Grove membership
Go Pro

Teams

For companies that want one context for every teammate's AI.

Early access

  • A Grove for your org
  • Teams and roles
  • Ask across your team's context
  • Company graph
  • Priority support
Join the waitlist

Stop re‑explaining yourself.

Early access for people, teams and AI builders. No spam, ever.