Nimbus 3.0 · Usage guide v1.0 · October 2026
Nimbus is Magic Bullet's client-state server for Claude. It holds a short, current record of each client engagement (what was decided, what shipped, what's open) so that any Claude conversation, in any project or in Claude Code, can pick up where the last one stopped instead of rediscovering everything.
In Maceo's words, Nimbus is "the sandpaper that rubs off the rough edges of Claude and my workflow."
The one rule: private unless promoted
Nimbus assumes every conversation is private. Everything you or your Claude write to Nimbus lands in your own private channel. Nobody else sees it, including the fact that a client name exists in your notes.
Other people see only what you promote: a cleaned-up summary (a snapshot) of one client that you deliberately publish to everyone. Nothing is shared by accident, and anything shared says who shared it and when.
Getting connected
In claude.ai. Your admin adds Nimbus once for the whole team. Then:
- Open Settings > Connectors (your own settings, not Organization settings).
- Find Nimbus and click Connect.
- Sign in to MB Portal with your email, password and authenticator code, then click Allow.
That's it. You don't do this again unless you're asked to disconnect and reconnect after an update.
In Claude Code. Nothing to set up. If your Claude Code is signed in with your claude.ai account, Nimbus comes along automatically. Start a new session after you first connect in claude.ai.
If Claude says you're "not a Nimbus member," your Portal account works but hasn't been added to Nimbus yet. Ask Maceo. You won't need to reconnect once you're added.
Day to day
You mostly don't operate Nimbus yourself. You talk to Claude, and Claude reads and writes Nimbus for you.
- Starting work on a client: just name the client. Claude reads its record before answering.
- Recording something: "Log that we moved the kickoff to Friday." Decisions, things shipped, findings and notes all go in the client's log.
- Keeping the record current: you never press save. When a client's log gets more than three entries ahead of its summary, Nimbus tells Claude to bring the summary up to date before doing anything else, and Claude does it without asking you.
Promoting: sharing a snapshot with everyone
Say "promote the PianoPiano snapshot" (or whichever client). Promoting always takes two steps:
- Claude shows you the exact text that would be published and points out anything that looks sensitive: personal opinions, misgivings, money about a person, health or family matters, things said in confidence. Nothing is published yet.
- You decide. Ask Claude to remove anything you don't want shared. When the text is right, say so, and Claude publishes it.
Beware: Claude isn't tuned to what you consider sensitive or embarrassing, and it might not know. Read the text yourself before you approve it.
Once promoted, everyone reading that client sees it labelled "promoted by [you] on [date]." A promotion can't be taken back, because others may already have read it. Promote again to replace it with a newer version; earlier versions are kept as history.
Only the summary is ever promoted, never the log behind it. Your thinking out loud stays yours.
Things said in confidence
If you say something you wouldn't want repeated, a private opinion of a person, a deal or yourself, tell Claude: "log that as confidential."
- Nimbus stores it but withholds its text from everything Claude normally reads, so Claude can't repeat it.
- It never goes into a summary, so it can never be promoted.
- To see it again, ask: "show me the confidential entries for [client]."
When other people are in the room
Your private notes are private from other Nimbus users, not from people who can see or hear your screen. In your own sessions, Claude reads your notes and may quote them.
- Mark private remarks confidential when you make them (see above).
- If Claude starts repeating something you don't want said, tell it to stop. Nimbus's rules tell it to stop when asked.
What Nimbus tells you
Sometimes a reply opens with a short note from Nimbus:
- 🔁 Consolidate first: a summary is out of date and Claude is updating it. Nothing for you to do.
- 📣 Catch-up: someone promoted a newer snapshot of this client since you last looked. Claude will tell you what changed.
- ℹ️ / ⛔ Notice: news about Nimbus itself, such as a new feature or a renamed client.
Finding the right client
You see client names that are yours plus any that have been promoted. Before starting a new client, ask Claude to check whether it already exists, and if you're not sure, ask Maceo. Two names for the same client (pianopiano and piano-piano, say) split the history in two. Claude can merge your own copies if that happens.
If something goes wrong
| What you see | What to do |
|---|---|
| "Not a Nimbus member" | Ask Maceo to add your Portal account. No reconnect needed afterward. |
| Nimbus tools are missing in a chat | Turn Nimbus on in the chat's tools menu, or disconnect and reconnect it in Settings > Connectors. |
| Asked to sign in again | Sign in to MB Portal as before. Sessions stay signed in for weeks, so this is rare. |
| A new feature isn't available yet | claude.ai remembers each connector's tools. Disconnect and reconnect Nimbus once. |
| Claude says a client doesn't exist | It may be someone else's private client. Ask them to promote it, or ask Maceo. |
For developers
How Nimbus is built and run (endpoint, sign-in through MB Portal, channels, the bulletin, migrations, deploys): see DEVELOPMENT.md in the repository (Magic Bullet access required).
Nimbus lives at mb-nimbus.io. The connector address is https://mcp.mb-nimbus.io/mcp.