Connectors

Connector basicsCopy Anchor Link

A connector gives Inspect tools from another service. The service may ask each person to authorize their own account, or an administrator may configure shared organization credentials.

Browse and configure connectors in Customize → Connectors.

Personal connectorsCopy Anchor Link

Personal connectors use credentials belonging to the person who connected them. Choose this when actions should use your identity, permissions, and audit trail. Other users connect their own accounts separately. Personal credentials do not automatically make a session private; connector access level controls session visibility.

Organization connectorsCopy Anchor Link

Organization connectors use credentials managed for the workspace. Choose this for a service account or shared dataset that should behave consistently for everyone. Only workspace administrators can create or change them.

Private connectorsCopy Anchor Link

A private connector is allowed only in private sessions. Using it makes the session private so sensitive credentials, personal data, and tool results are not exposed through a public session. Mark a connector private whenever its data or authorization should not be visible to the whole workspace.

Custom MCP serversCopy Anchor Link

Add a custom connector when your tool is exposed through a remote Model Context Protocol (MCP) server. Inspect accepts remote HTTPS servers, including OAuth and secret-backed headers; local command and stdio servers are not supported. Expose only the tools users need and avoid putting credentials directly in the server definition.

For credential handling, authorization boundaries, provider responsibilities, and current limitations, see MCP connector security.