Complete MCPHub setup first

Run the setup wizard and choose generic JSON. Keep the actual command, args, env, and entry ID. All values below are examples.

Add the local connector

Add a stdio connection through the Claude Code CLI. This example uses user scope:

claude mcp add --transport stdio --scope user work-projects --env MCPHUB_HOME=/Users/you/.mcphub -- /absolute/path/to/mcpbridge connect --profile work --client ci_example

Everything after -- is the connector and its arguments. On Windows, use the actual exe path and quote paths containing spaces.

You can also merge the generated mcpServers entry into .mcp.json at the project root. Personal paths and entry IDs are unsuitable as shared team configuration; each person should create their own entry.

Check the connection

claude mcp list
claude mcp get work-projects

Inside Claude Code, use /mcp to inspect status. Project servers may require trust confirmation and enablement. Saving configuration does not prove a working connection; run MCPHub doctor for the actual entry as well.

Disable or remove a connection

Manage the client-side connection through /mcp, or remove this example with claude mcp remove work-projects --scope user. To stop that entry from accessing MCPHub, revoke its grant separately in your personal portal.

Official reference

See the official Claude Code MCP documentation for command syntax, scopes, and server status.