Connect SeggWat to Claude in One Click

A while back I wrote about why I built an MCP server into SeggWat. Short version: feedback is only useful if you actually look at it, and the place I already work is my AI assistant. So I made SeggWat's data queryable from any MCP client.

That post skipped the boring part. To connect it, you had to generate an API key, hunt down your client's config file, and paste in a JSON block with the right header. Fine if you're technical. A wall if you're not.

That step is gone. SeggWat is now a Claude custom connector. You add it the way you'd add any other connector: paste one URL, log in, click Allow.

How to connect it

In Claude, open the connector settings and add a custom connector. Paste your SeggWat MCP URL:

https://seggwat.com/mcp

Claude sends you to a SeggWat login. If you're already signed in to your dashboard, you'll just see a consent screen. Click Allow and you're done. No API key to copy, no client ID, no config file.

From there you can ask Claude things like:

• "What bug reports came in this week?"
• "Summarize the feedback on our new checkout flow."
• "Draft a changelog entry for the latest release and publish it."
• "How did our last NPS survey score?"

Same tools as before (feedback, ratings, surveys, changelog), just without the setup tax.

The part that took the longest: OAuth

Claude's custom connector dialog is OAuth-only. There's no field for a static API key. So to be connectable at all, the MCP endpoint has to advertise OAuth metadata and run a real authorization flow. That turned what I assumed was a one-URL job into a proper project.

Two decisions made it work the way I wanted.

The first was leaning on Dynamic Client Registration (RFC 7591). Instead of asking every user to create an OAuth app and copy a client ID and secret, the endpoint advertises a registration route and Claude registers itself. The user types a URL and nothing else. That one spec is the whole difference between "paste this link" and "go to your dashboard, create an app, copy these three values, come back."

The second was making SeggWat its own authorization server instead of handing the flow off to my upstream identity provider. The catch with proxying is that the upstream login page can't see SeggWat's own session cookie, so a user already signed in to the dashboard would get asked to log in a second time mid-flow. By issuing the tokens myself, a logged-in user just sees a consent screen and clicks once. The token Claude ends up with is an ordinary SeggWat access token. It shows up on your API keys page, and revoking it is the same as revoking any other key. None of the existing API auth had to change to support it.

If you want the full shape: RFC 9728 for the protected-resource metadata, RFC 8414 for the authorization-server metadata, S256 PKCE on the code exchange, and a short-lived single-use code in between. Most of the actual work was the discovery routes and getting PKCE exactly right. Once those were in place, Claude figured out the rest on its own.

Why bother

Two reasons.

The obvious one is reach. Most people who collect feedback are never going to hand-edit a JSON config to wire up an MCP client. A connector you add by pasting a URL is something a non-engineer can actually do, which means the AI workflows I find useful are now available to the whole team, not just whoever owns the terminal.

The less obvious one is where this is all heading. I said in the last post that the SaaS tools that survive will be the ones natively accessible to AI workflows. "Has an MCP server" was step one. "You can connect it to your assistant without reading the docs" is step two. The bar keeps sliding toward zero friction, and I'd rather be ahead of it.

Try it

If you already use SeggWat, open Claude, add a custom connector, and paste https://seggwat.com/mcp. That's the whole setup.

If you don't yet, sign up at seggwat.com, drop one script tag on your site, and you'll have feedback flowing in minutes. Then connect Claude and ask it what your users are saying.

EU-hosted, GDPR-friendly, screenshot annotation, surveys, an ideas portal, and now a one-click Claude connector. $6/month, 14-day free trial.