Use SoWhatify from any AI

SoWhatify is a remote MCP server. Any MCP client can connect to it and use your lenses, chains and personas on whatever you are reading.

  1. Build private lenses, chains and personas in conversation.
  2. Browse the public marketplace for inspiration.
  3. Run run_lens or run_chain on any URL or pasted text.
  4. Publish on the website when you want to share.
  5. Triage what people send to your Dropboxes.

Dropboxes are pages you send to someone without an account: they upload a document, it runs through one of your lenses, and you both get the analysis. Your client can read them with list_dropboxes and list_dropbox_submissions and talk you through what came in. Creating one, changing its provider key or switching it off stays on the website — each is a public-facing act involving a credential.

Your client is the model — SoWhatify supplies the perspective, the profile slice and the structure. Nothing you make here is public until you publish it yourself.

Connect

Most clients need no token. Claude, Cursor and Zed sign you in through your browser: you approve once, and the client keeps its own key after that. Leave every token and header box empty.

You only need a token if your client has no sign-in step — a config file, or an older IDE. Then you paste your personal token into an Authorization header.

So: if a client offers to sign you in, let it. Copying a token in by hand is the long way round, and easy to get wrong.

Claude Desktop connects with just the URL below — it opens an authorization page in your browser, and approving there is what gives it a credential. Leave every token and header field empty.

  1. Settings → Connectors → Add custom connector
  2. Paste the URL below and name it (anything you like)
  3. Authentication: leave "Sign in now" selected
  4. OAuth client: leave "Use Claude's published identity" selected
  5. Leave Request headers empty, click Add, then approve in the browser
  • Nothing goes in Request headers. That box is for servers that want an API key; here the approval page hands Claude its own credential and Claude stores it.
  • Claude may show "No sign-in — Detected" next to the third option. Ignore it: it comes from one open endpoint used for discovery, and sign-in works.
  • No account needed. The approval page can create one for you with no email, and you can attach an email later without losing anything.
  • Use the token below only if you pick "No sign-in" on purpose, or use the older config file — everything else is tokenless.
Prefer a token, or an older build without the Connectors panel?

Two token routes, both equivalent. In the Connectors dialog: pick "No sign-in", then Add header with name Authorization and value "Bearer <your token>". Or, on an older build: Settings → Developer → Edit Config, add this to claude_desktop_config.json, restart. Either way you are replacing the browser sign-in, not adding to it.

Claude Desktop MCP documentation

Do you need a token?

Only if your client has no sign-in step. Claude (desktop, web and Code), Cursor and Zed all open an authorization page instead — approve it once and they hold their own credential, so every token and header field in their setup dialog stays empty. A config file, or a client you deliberately set to “no sign-in”, needs your personal token as an Authorization header:

Account & connections Sign in by email

No account? Connect anyway

No sign-up either way. A client that signs in through the browser offers this on the approval page itself — “Continue without an account” — so you need nothing from here. The button below is the token version of the same thing, for a client that cannot sign in. Either way you get a private id and can build lenses, chains and personas (never publish) with generous limits. Add an email later to publish and sync across devices — your id and everything you built are kept.