# Use MCP Hub

1 min read

## User Flow

1. **Add the MCP server URL.** The user or IT-managed configuration points the MCP client to the published virtual server URL.

2. **Authenticate to the hub.** The client follows MCP OAuth metadata, starts authorization, and receives hub-scoped tokens after sign-in.

3. **Complete downstream logins.** If a selected origin requires per-user credentials, the hub guides the user through that login once and stores the token securely.

4. **Discover tools.** The MCP client lists the curated tools, prompts, and resources exposed by the virtual server.

5. **Run tool calls.** Every call is checked by the hub, routed to the correct origin, and executed with the correct user credentials.

## Client Experience

| One server | Curated surface | Re-auth when needed |
| --- | --- | --- |
| The client connects to one MCP endpoint even when the workflow spans multiple enterprise systems. | The user sees only the tools selected for the virtual server and their access rights. | If downstream tokens expire, the hub can prompt the user to refresh authentication without exposing origin secrets. |

**Simple explanation for users.** Sign in once to the company hub, connect the systems you are allowed to use, and let your AI assistant call those approved tools through one governed endpoint.