How to add Claude connector?

[tonedice]

After entering the mcp url it asks to connect. Then in browser it asks for a bearer token. where to get it?

[tonedice]

From rahil on X: "You can use any passphrase when you’re setting up in Cloudflare. The token is your password to secure your memories"

[greyseymour]

Commenting here because while @tonedice 's Rahil comment is helpful, there may still be room for confusion... typically I am used to generating bearer tokens on a case-by-case basis... in this scenario, my bearer token was the password I setup when setting up SecondBrain - nowhere in the interface to generate a new bearer token as one might expect, and not much help querying the term "bearer token" in the Docs...

I love Secondbrain, it's architecturally sound, but I think some of these UX/UI hurdles (whether quirks like this one, the hyper-minimalist desktop interface, the connections page ONLY being accessible via a menubar dropdown with the mac app open - e.g., NOT accessible from a Settings gear/icon inside of the app itself as one might expect) could truly hold back well-meaning less-technical folks from using SB!

I am in the midst of a huge 16+ entry landscape analysis of all second-brain/persistent memory services for agents I can find, and SB is in the upper echelon in terms of architecture & philosophy... but not at all in the actual UX department. :( (It does LOOK good, tho!!)

[tonedice]

Agree with the UX/UI problems you mentioned. Looking forward to getting this more clear and less confusing :)

[rahilp]

@greyseymour @tonedice first, thank you. This is the kind of feedback that actually makes the product better, and the fact that you wrote it up while running a full landscape analysis means a lot.

You are right on every point, and the token question in this thread is the clearest example of it. Here is what is going on and what we are doing about it.

Bearer token confusion. Your bearer token is just the password you chose when you set up Second Brain. The real problem is that the installer calls it a "password" while the dashboard login calls it a "Bearer token," and nothing tells you they are the same value, so it reads like something you are meant to generate. Two fixes are now tracked:

• Clarify that your "bearer token" is the setup password (terminology + docs) #231 reconciles the wording across the app and adds a proper "what is my bearer token" entry to the docs, so searching for it actually answers the question.
• Generate, name, and revoke additional access tokens (per-client, rotatable) #233 is the bigger one you expected: generating, naming, and revoking separate tokens per client instead of reusing the setup password everywhere.

Connections only in the menu bar. Agreed, it should be reachable from inside the app window too. The backend already supports opening that view, so this is mostly adding a visible settings entry point. Tracked in #232.

The minimalist / discoverability point. This is the one I most appreciate you naming, because it is the easiest thing to go blind to once you have built it. We are treating it as its own pass, not a one-off, tracked in #234, with a firm rule that we do not touch the visual language you liked and only make it easier to find where things live.

None of these are "someday." #231 and #232 are first up. If your analysis surfaced other UX notes, I would genuinely like to see them. Thanks again for the kind words on the architecture and philosophy.