Agent Hub Get started ↗

SHARED MCP CONFIGURATION

One MCP definition. The clients you choose.

Stop maintaining the same server definition in several client configs. Collect the copy you trust into Hub, then review its delivery to Claude Code, Codex or DeepSeek Harness.

Reviewed changes, per-server choices and recorded recovery. Client permissions still apply.

Agent Hub inventory showing shared resources and supported clients
Real Hub overview with fictional resources. No credentials or personal settings.

Know which copy each client uses.

Share one server first.

  1. Inspect the existing copies

    Open MCP servers in Hub and compare the trusted Hub and client definitions.

  2. Review the direction

    Import a client copy into Hub, or deliver Hub settings to one client. Each action opens its own preview.

  3. Apply and verify

    Apply the reviewed change, restart the affected client and test the connection when ready.

Before you start

Does every client share one running server?

Not necessarily. Hub shares configuration and client-specific launchers. It does not combine provider subscriptions or guarantee a single shared process.

What if a client copy is intentionally different?

Keep that client’s settings. Hub does not silently pick a winner for real differences. Recovery is recorded, but later edits can block an unsafe rollback.

Use one harmless server as your first check.

The guide explains import, delivery, connection testing and recovery before you change the rest of your setup.

See the steps ↗