Connect an MCP host without copying bearer tokens

• Use a host that supports remote MCP servers and OAuth discovery.
• Confirm the PipeLedger workspace has at least one approved, published data mart that the connection may use.
• Authorize with an active PipeLedger member account that has a human connected-app policy, or obtain an organization Credential ID and client secret from an Owner or Admin through an approved secret manager.

Human member authorization requires PipeLedger's normal secure sign-in and multi-factor authentication. Organization credentials are a separate machine-authorization path; they do not bypass or reset a person's account security.

1. Add https://mcp.pipeledger.ai/mcp as the remote MCP server in the host.
2. The host discovers PipeLedger's protected-resource and authorization-server metadata. PipeLedger validates the host's Client ID Metadata Document, dynamic registration, or managed registration before authorization continues.
3. Choose Sign in with PipeLedger or Use organization credentials.
4. Record the connection name, use case, and business purpose. Review the effective tools, marts, role, clearance, and scope before approval.
5. PipeLedger returns to the host's validated callback. Start a new conversation and make a representative read request to confirm the expected tools and data boundary.

Member authorization

A member signs in, completes required identity security, and approves access under the Owner/Admin-assigned connected-app policy. Fresh consent defaults to that approved envelope; the member explicitly chooses Viewer or Operator and may limit the app's capabilities, but cannot expand them. PipeLedger persists that role selection verbatim and derives only the connection name from validated client metadata. Optional use case and business purpose remain member-supplied.

Organization credentials

An existing PipeLedger Credential ID and client secret prove the organization authorization source. The host receives a distinct OAuth grant and bearer; it never receives the organization client secret as its runtime access token. Disabling the source credential revokes every active connection derived from it.

Access tokens last up to one hour. When the host receives offline_access, it can use a rotating refresh token with a 30-day lifetime. Each successful refresh replaces the prior refresh token.

Owners and Admins can tighten a connection's source policy without reconnecting the host. The next request uses the current policy. If the allowed-tool set changes, PipeLedger expires the MCP session so the host can initialize a truthful tool list while the OAuth grant stays active.

Revoke a connection from the Connected Apps area when host token material may be compromised. Revocation invalidates its access token and entire refresh-token chain.

Authorization is denied

Ask an Owner or Admin to verify the member or organization credential's connected-app policy. Changing a person's general workspace role is not automatically the correct fix.

The host connects but expected tools or data are absent

Confirm the connection permits those tools and marts, and confirm the required delivery is approved and published. Refresh the host's app metadata when its developer workflow provides that action, then begin a new conversation.

A member lost access to their authenticator

Use PipeLedger's ordinary account-recovery flow. Reconnecting an MCP host cannot bypass MFA, and an Owner, Admin, or support agent cannot reset another person's authenticator or recovery codes.

For pre-subscription questions or sign-in trouble, email support@pipeledger.ai. PipeLedger targets an initial response within one business day.

Subscribers can use the secure in-app Communication Hub for live support when available or tracked tickets at any time. Never send passwords, client secrets, access tokens, authenticator or recovery codes, or financial records through email or chat. See the public support page or return to the MCP server documentation.