Profiles and clients

How a client picks its servers#

When you click Connect to Toolport, Toolport writes a gateway entry with env vars into the client's config:

• TOOLPORT_CLIENT_ID — identifies the client, so the gateway resolves its profile live.
• TOOLPORT_PROFILE — pins the client to one profile. Unset means it follows the active profile.

Credentials belong to servers#

Credentials are stored per server, not per profile. To use two accounts for one service, add the service twice ("GitHub (work)", "GitHub (personal)") and enable one in each profile. Tool names are namespaced per server (server__tool), so they never collide.

One gateway per host#

Client-spawned stdio gateways use a small adapter by default, and one host daemon owns the router and shares downstream connections. To go back to separate in-process gateways, set "gatewayTopology": "legacy" in registry.json and restart connected clients, or set TOOLPORT_GATEWAY_TOPOLOGY=legacy for one client.

Control over tool calls#

Global settings in the app apply to every client:

• Lazy discovery — on by default. See Discovery modes.
• Destructive-tool block — require approval before destructive calls.
• Disabled tools — hide individual tools.
• Activity — review calls and catalog bytes avoided.