Getting connected

The server

One address, one scope, one sign-in. These are the only values you need, whichever assistant you are connecting.

Connecting Claude

The connection belongs to your Claude account, not to a device. Add it once and every place you sign in to Claude has it.

On the website or in the desktop app

1. Open Settings, then Connectors. In the desktop app you can also click + beside the message box, then Connectors, then Manage connectors.
2. Choose Add custom connector.
3. Name it HubPeople. The name is only a label in your own list, but using the same one keeps these guides matching what you see.
4. Put https://mcp.hubpeople.ai/mcp in the server address field and continue.
5. Leave every remaining field exactly as it arrives. They are filled in from our server and there is nothing you need to change.
6. Sign in with your HubPeople account when the browser opens, and approve the access.

This route is identical on a Mac and on Windows.

Tool permissions

Out of the box every single request asks your permission first. The tools are labelled, so you can wave through the ones that only look at things and stay asked about the ones that change something.

In the connector's permissions, set the read-only tools to Always allow and leave the rest. Nothing in that group can change a page.

Connecting another agent

Nothing about this server is specific to Claude. It implements the MCP authorization spec, so any client that does too can connect itself without us issuing you anything. For most of them the only thing you have to provide is the address at the top of this page.

Connecting Grok Bot

Grok Bot can add the connection itself. Ask it:

1. Type the address exactly as written: lower case, no slash at the end. HubPeople is not in Grok Bot's list of connectors, so it has to be added by its address.
2. When a connect card appears in the chat, sign in with your HubPeople login and approve. There is no token or key.
3. That's it. Grok Bot can now see the brands your HubPeople account can see.

To use the toolkit too, ask it to set up the HubPeople toolkit. The connection tells it where to get it.

What a compliant client does

1. Calls the endpoint with no token and gets 401 with a WWW-Authenticate: Bearer challenge naming the resource metadata document.
2. Reads the protected resource metadata to find the authorization server.
3. Reads the authorization server metadata to find where to register itself and where to send you to sign in.
4. Registers itself at the registration endpoint. Dynamic client registration is open, so there is no client id to request from us and no secret to keep.
5. Runs an authorization code flow with PKCE. You sign in and approve in a browser, and it exchanges the code for a token.
6. Sends that token as a bearer header, and refreshes it when it expires.

What your client needs from you

• The address, and nothing else. The server publishes its OAuth metadata at the standard well-known addresses, so a client that follows the spec reads its own configuration from there. You should not have to paste endpoints in by hand, and you should not hard code them: if we ever move them, a client that discovers them follows, and one that has them written down breaks.
• There is no client id to ask us for and no secret to keep. Registration is open, so your client registers itself the first time it connects. If a set of instructions tells you to email us for credentials, it is not describing this server.
• PKCE has to be S256. A client offering only a plain challenge is refused, and the failure is not always reported clearly at the other end.

Redirect addresses, including loopback

A command line tool or a desktop agent has no website to come back to, so it listens on a port on your own machine and uses that as its redirect. The server accepts loopback redirects, which is what makes those clients possible at all.

Which tools work today

As each one is confirmed, its own steps get added to this page, and the change is recorded in the Changelog at the bottom.

When it stops working

Limits and rules

• On the Claude Free plan you get one custom connector. If you already have one, you will have to remove it or move to a paid plan.
• On a Team or Enterprise plan, only an organisation Owner can add a connector. If there is no way to add one in your settings, that is why. Ask your Owner to add it once for the organisation.
• On a shared computer, sign out of HubPeople first. A sign-in can be reused for a while in the same browser, so on a machine other people use you could end up joined to whoever signed in before you.
• You see exactly what your HubPeople account sees. The connection carries your own permissions. It cannot reach a brand you could not already open in the portal.
• We do not issue access tokens to partners. Signing in through your assistant is the only route, and it is the one we support. Anything asking you to paste a key is not us.
• To disconnect, remove the connector in your Claude settings. That discards the tokens the client is holding. Reviewing and ending sessions from the HubPeople portal is not built yet, so if you are ever unsure, remove the connector and add it again.

Installing the toolkit

Optional, and separate from the connection above. The connection lets your assistant see and change your brands; the toolkit carries the guidance it follows while it works on them, so building, auditing and migrating pages is more capable with it than without. It is one download from our public GitHub release, the same for every brand.

The steps are on Connect your brands to AI.

Where next

Once you are connected, the start page shows what to do with it.

Connect your brands to AI →

Everything the MCP can do →

Tell us what you think

This is a beta, and connection problems are the ones we most want to hear about. If something here did not match what you saw, tell us and we will fix the page.

Send feedback

Changelog