AI memory infrastructure

The thread that connects your AI tools.

Skein is memory infrastructure, not another notes app. Connect once over MCP, and Claude, Cursor, ChatGPT, and every compatible client can search your memory and capture new thoughts. You scope every connection, see what each tool has touched, and turn any one off on its own.

Works with any AI tool that supports MCP servers.

Skein personal MCP endpoint connected to multiple AI assistants

Memory infrastructure, not another notes app.

Your AI tools are the product. Skein is the thread that makes them remember you across providers, contexts, and subscriptions.

One personal endpoint

Every account gets a unique MCP URL with rotating OAuth credentials. Paste it into any MCP-compatible client, and every assistant can search your memory and capture new thoughts.

Capture as you work

A connected assistant stores a thought over MCP while you are in the middle of something, with no notes app to open and no manual organization. When you want to jot something down with no tool open, there is a web capture box too. Either way, thoughts land on the thread and stay searchable.

Hybrid search that just works

Vector similarity, full-text search, recency decay, and entity extraction, without tags, folders, or manual organization. “What did the contractor quote for the deck” finds “Mike said $14k for cedar.”

Cross-tool by design

Stop re-explaining yourself every time you switch assistants or subscriptions. Your memory follows you instead of staying locked inside one provider’s product.

Control every connection

Scope each connected tool to read or write, see when it last reached your memory, and revoke any one on its own. A tool that only needs to look things up never gets permission to change anything, and you can limit any of your agents to specific namespaces, with read, write, or full access set per space. A pasted connection token can be scoped to read only and set to expire, so it is no riskier than a one-click approval.

Secrets stay out of your memory

When a capture contains something like an API key, an access token, or a private key, Skein holds that thought aside before it can spread. It is still saved, but it stays out of search and out of reach of your connected tools until you resolve it in your security settings, where you can clear it, redact just the secret, or let it through. Available on Pro and Max.

Know where each memory came from

Every memory records which tool wrote it and when, with the history of how it changed. Trace why your AI believes something about you, see what a thought said before it was edited, and correct it at the source.

Separate spaces by context

Keep work in one space, personal life in another, and a specific client or project in its own, so the right memory shows up in the right place and nothing bleeds between them.

Share a space, read only

Hand one namespace to someone and their AI tools can read that thread, while the rest of your memory stays private to you. It is what you want when a client, a work project, or something personal like a trip you are organizing needs context that more than one person's assistant can pull from, instead of each person re-explaining the same background. People you share with can see the space, not change it. Available on Pro and Max.

Bring your own key

On Max, connect your own OpenAI-compatible API key. Skein routes the work of turning captures into searchable memory through your provider instead of ours, so your monthly capture limit goes away. You pay your provider directly for that processing.

Portable by default

Export to JSON any time. Point your own MCP client at Skein. Your memory belongs to you, not the provider.

Privacy without lock-in

Built for people who want AI memory persistence without handing years of context to a single vendor. Complements provider-native memory; it does not replace your tools.

Skein search answering "what's my favorite coffee?" with a via ChatGPT provenance badge

End cross-tool amnesia.

You explained a project to one assistant last month, but you are working in another today, so you start over, abbreviate, and lose detail every time. Skein keeps one thread every MCP client can pull from, so context survives subscription changes and new tools.

See features →
Skein MCP page with a personal memory endpoint and client setup for Claude, Cursor, and ChatGPT

Connect once. Recall everywhere.

Sign up, copy your personal MCP endpoint, and paste it into the AI tools you already use. From that point forward, search your memory and capture new thoughts without rebuilding context in each app.

View pricing →
Skein MCP connections list showing scope, namespace access, activity counts, and revoke controls

See and control what your tools can do.

Connecting several AI tools to one memory only feels safe if you can see what each of them does with it. Skein scopes every connection to read or write, logs when each tool reaches your memory, and lets you revoke any one without touching the others. When a capture contains something like an API key, Skein holds it aside before it can spread into your searchable memory. Every memory carries where it came from and how it has changed, so you can trace what your AI believes about you and fix it at the source.

How we handle trust →
Skein namespaces page with work and personal spaces and shared-namespace tabs

Built for people juggling more than one context.

Consulting clients in one tool, personal projects in another, side work in a third. Your work is not owned by a single workspace, and your memory should not be either. Skein keeps neutral infrastructure between the tools you choose.

Read the FAQ →
Skein recent thoughts feed with via Claude and via ChatGPT provenance on each capture

No app to open. It works inside your tools.

Your connected assistants capture new thoughts and recall what you need as you work, through MCP, so there is no destination app to check. When you want to drop a thought with no tool open, the web capture box is there too.

Start capturing →

Connect everything

On every plan

Bring your own key

On Max

Scoped and revocable

Control what every connected tool can do

Plans for heavy use.

Connect every MCP client on every plan. Connection is never gated behind payment. Free is enough to feel the real thing. Pro raises your monthly captures and turns on secret scanning and namespace sharing. Max takes captures higher, makes namespaces unlimited, and lets you bring your own key for captures with no monthly limit. Pay monthly, or choose annual and get two months free.

Frequently asked questions

What is Skein?
Skein is hosted personal-memory infrastructure: the continuous thread your AI tools read from and write to via MCP. The name Skein comes from the idea that a skein is a loosely wound, coiled length of yarn or thread. That image is the inspiration for how we think memory should work across multiple AI contexts. Connected assistants capture and recall through MCP; the web capture box is there when no tool is open.
How do you pronounce Skein?
Skein rhymes with Brain, same ending sound (-ain). Think "skayn," like brain with an sk at the start.
Which AI tools work with Skein?
Any AI tool that supports MCP servers. Skein exposes a personal OAuth-secured MCP endpoint. Paste it into Claude, Cursor, ChatGPT connectors, Claude Code, or any compatible client. If the tool speaks MCP, it can use your memory.
How is this different from ChatGPT memory or Claude projects?
Provider memory stays locked to that provider. Skein is neutral infrastructure: one personal endpoint that follows you across every MCP-compatible client. Switch assistants without rebuilding years of context.
How is this different from Mem, Reflect, or Notion AI?
Those products are notes apps with AI features; the app is the destination. Skein is memory infrastructure. The AI tools you already use stay the product; Skein makes them more useful.
Is Skein a notes app or second brain?
No. Skein is not trying to replace Notion, Obsidian, or Evernote. There is no manual backlink graph. Recall happens through AI search, not note organization. It complements your tools instead of competing with them.
What do I get on the free plan?
Five hundred thought captures per month, up to two thousand thoughts stored, three namespaces, unlimited MCP connections, and unlimited search. Enough to feel the real product, with room to grow on Pro and Max.
What do the paid plans add?
Pro is $12 a month at the founding rate. It raises you to ten thousand captures a month, unlimited storage, and ten namespaces, and turns on secret scanning and namespace sharing. Max is $39 a month. It adds fifty thousand captures a month, unlimited namespaces, and the option to bring your own key, which removes the monthly capture limit. Both paid plans are also available annually, with two months free.
What is secret scanning?
As you capture, Skein checks each thought for things like cloud keys, payment keys, source-host tokens, and private keys. When it finds one with high confidence, it holds that thought aside: the thought is saved, but it stays out of search and out of reach of your connected tools until you resolve it. You can clear it, redact just the secret, or let it through. Secret scanning is on for Pro and Max.
Can I bring my own API key?
Yes, on Max. Connect your own OpenAI-compatible key, with an optional base URL if you use another provider. Skein then routes the embedding and entity work through your provider, your monthly capture limit goes away, and you pay your provider directly for that processing.
Can I share a namespace with someone, and who can see it?
Yes, on Pro and Max. You share one namespace at a time, read only, so the people you share with can see that thread while the rest of your memory stays private to you. Access is opt-in on both sides. You and the other person connect first, each agreeing to that, and a namespace you offer only becomes visible to them once they accept, so nobody lands in your space by surprise. They see your public profile and the thoughts in the shared namespace, nothing else about your account, and every memory still shows which tool wrote it. Share a namespace with as many people as you want, and remove anyone's access at any time without affecting the space for everyone else. Your own agents are handled separately: you choose which of them can reach a namespace, and whether each one has read, write, or full access to it.
Can I import my existing memory?
You can import a Skein export any time, on every plan, so moving between accounts or restoring a backup is a round trip. Bringing in history from ChatGPT, Claude, Notion, and plain text files is coming soon.
Can I export my data?
Yes. Export to JSON any time and connect your own MCP client. Portability is a core feature. Your memory is yours.
Who is Skein for?
AI power users paying for more than one subscription, people whose work spans clients and projects, and privacy-conscious users who want memory persistence without vendor lock-in.

Connect your tools. Keep one thread.

Stop re-explaining yourself every time you switch assistants. Memory infrastructure that works where you already work.