Noosphere

Working memory of your context for AI tools.

Your thinking is scattered across threads, tools, and devices. Each conversation is a silo — what you figured out in one doesn't exist in the other.

You refine an approach with Claude, then open Cursor and have to explain it all over again. You brainstorm on your phone, then sit down at your desk and it's gone. The thinking lives in context windows and people's heads — and both get cleared.

Code lives in git. Tasks live in Linear. Docs live in Notion. But the layer underneath — the brainstorm that hasn't become a decision yet, the decision that hasn't become code yet, the why behind every what — has nowhere to go. Noosphere is that layer. (Full story)

---

How it works

Noosphere is an MCP server. Any AI tool that supports MCP can connect to it — Claude, ChatGPT, Cursor, or anything else. They all share the same memory.

It stores two things per project:

• Project state — a living document that's always current: decisions, what's in progress, next steps. Updated and pruned as things change.
• Entry log — an append-only history of work summaries, brainstorms, and decisions you can search and read.

The AI discovers Noosphere automatically and uses it behind the scenes. You don't need to learn any commands — just talk naturally:

"What were we working on?" "Remember this decision" "Save where we are"

---

Connect your tools

Noosphere is hosted at usenoosphere.ai. Connect as many tools as you want — they all share the same memory.

https://usenoosphere.ai/mcp

Claude.ai

Customize → Integrations → Add → paste the URL above.

ChatGPT

Settings → Apps → Create → paste the URL above. Requires Pro, Team, or Enterprise with Developer Mode enabled. In the description field, paste:

Persistent memory across conversations. Browse at the start to pick up where you left off. Save when a decision is made or the session ends. Use automatically — the user doesn't need to ask.

Claude Code

claude mcp add noosphere --transport http --scope user https://usenoosphere.ai/mcp

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "noosphere": {
      "url": "https://usenoosphere.ai/mcp"
    }
  }
}

Codex

Add to ~/.codex/config.toml:

[mcp_servers.noosphere]
url = "https://usenoosphere.ai/mcp"

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "noosphere": {
      "serverUrl": "https://usenoosphere.ai/mcp"
    }
  }
}

Any other MCP tool

Point it at https://usenoosphere.ai/mcp. OAuth will prompt you to log in.

---

Using it

Projects

A project is just a name — "my-novel", "home-automation", "learning-rust", whatever you're working on. No setup needed. The AI creates projects automatically the first time it saves something.

For git projects, the AI typically picks up the project name from the remote URL. Any tool using the same project name shares the same memory.

The rhythm

1. Start — the AI loads your current state and picks up where you left off
2. Work — the AI saves context at natural checkpoints: decisions made, milestones reached, direction changes
3. Stop — say "save where we are" so the next session (in any tool, on any device) knows what comes next

---

Works with Proto

Once your brainstorm becomes a decision, use Proto to turn it into a working prototype. Proto structures your project into a spec, plan, and tracked tasks. Subagents implement in parallel while you steer. Noosphere carries the context. Proto builds from it.

Self-hosting

You can run your own instance instead of using usenoosphere.ai:

git clone https://github.com/mmndaniel/noosphere.git
cd noosphere
npm install
npm run build
./start.sh

The server runs on port 3456 by default. Point your MCP client at http://localhost:3456/mcp. To stop: ./stop.sh

Without auth configuration, the server runs in open mode (single local user — fine for personal use). For bearer token auth, set NOOSPHERE_TOKEN. For full OAuth, configure Auth0 env vars — see .env.example.