Support
How to connect a chat, what to do when something does not work, and how to reach a person.
Connecting a chat
Give your client one address and nothing else:
https://resonance.parshkov.com/mcp
The client discovers OAuth by itself and opens the Resonance consent page, which asks you to sign in if you are not signed in already. You will never be asked to paste a key or a token; if something asks you for one, it is not this flow.
Signing in is what makes every surface one account. Connect Claude today and ChatGPT next week and both reach the same you — the same shared thoughts, the same matches — and there is somewhere to tell you when a new match appears.
- Claude
- Settings → Connectors → Add custom connector → paste the URL.
- ChatGPT
- Settings → Apps & Connectors → Advanced → Developer mode → Create → paste the URL, authentication OAuth → Scan tools. Developer mode is not available on every plan or workspace; if you cannot find it, your workspace policy decides.
- Grok
- Connectors → New Connector → Custom → paste the URL.
- Claude Code
claude mcp add --transport http resonance https://resonance.parshkov.com/mcp- Cursor, Windsurf, any
mcp.json {"url": "https://resonance.parshkov.com/mcp"}
Common situations
- Discovery says a share is required
- Nothing of yours is discoverable yet. Prepare a thought, read the preview, and confirm the share; then run discovery again. This is the service refusing to search on your behalf before you have agreed to take part.
- Discovery returns candidates but no resonances
- Candidates came back and none cleared the bar. That is an answer, not a failure: the engine will not advertise a match it cannot evidence.
- The page says
WebMCP · unavailable - Your browser does not expose
document.modelContext. That is the browser, not the service. Chrome 152 exposes it when started with--enable-features=WebMCP. The connectors above need no such thing. - A connected client asks you to authorise again
- Re-approving is harmless. As long as you sign in with the same provider account, every client you connect resolves to the same Resonance account.
- The consent page asks you to sign in and you thought you already had
- The page can only see a sign-in made from the same browser it opened in. If your chat client opened it somewhere else — another browser, a private window, an in-app view — sign in there too; it lands on the same account.
- You want something removed
- Revoke from your chat with
resonance_stop_sharing, or from the Collaboration panel on the site. Revoking takes effect immediately. To remove the account itself, ask below.
Reporting a problem
For a bug or a question, open an issue in the public repository, or write to the contact below. For anything involving security or another person's data, use the contact rather than a public issue.
Contact: mail@parshkov.com