AI connections and developer tools

Connect an assistant to Institution’s remote MCP endpoint

Use an MCP client that supports remote Streamable HTTP and OAuth.

Updated 2026-11-11

Connect a Google-created account to the MCP portal

The separate AI connection portal currently uses Institution email and password sign-in.

Updated 2026-11-11

Recover from an MCP sign-in cookie or form error

Reopen the sign-in page when the browser no longer has the expected form session.

Updated 2026-11-11

Understand Never expires for an AI connection

An open-ended grant still depends on valid identity, company access, and current permissions.

Updated 2026-11-11

Choose read-only access for an assistant

Use the consent presets, then inspect the actual selected capabilities.

Updated 2026-11-11

Reduce an assistant’s existing permissions

Edit permissions can remove capabilities from an active connection.

Updated 2026-11-11

Add a capability through a new consent flow

An assistant cannot expand its own grant from the permission editor.

Updated 2026-11-11

Distinguish portal sign-out from revoking an assistant

Use Revoke access when you want the agent connection to stop.

Updated 2026-11-11

Reconnect after MCP authentication is no longer valid

A confirmed invalid account session requires renewed sign-in and authorization.

Updated 2026-11-11

Review what an AI connection attempted

Agent activity shows operation names and outcomes rather than record contents.

Updated 2026-11-11

Understand why an approved MCP scope can still be denied

Connection consent works within your current company role and workflow rules.

Updated 2026-11-11

Read every MCP result page before treating a list as complete

A cursor or native pagination result means more records may remain.

Updated 2026-11-11

Recover safely from an uncertain MCP workflow result

Reuse the same request identity when a write result is uncertain.

Updated 2026-11-11

Check developer-management permissions and verification

API credential management can require company authority and a verified sign-in.

Updated 2026-11-11

Save a newly revealed integration credential

API keys, client secrets, and webhook signing secrets are shown once.

Updated 2026-11-11

Rotate an API key and update its server configuration

Rotation stops the current credential, so prepare the consuming integration before confirming.

Updated 2026-11-11

Plan for new consent after editing an app

Changing app settings revokes existing grants and requires fresh customer consent and review.

Updated 2026-11-11

Understand a private app’s beta company invitation

The invitation makes authorization possible; the customer still must approve access.

Updated 2026-11-11

Verify an app publisher with its displayed DNS record

Add the exact TXT record shown for the developer app, then run verification.

Updated 2026-11-11

Resolve an OAuth consent screen with no eligible companies

Eligibility depends on management permissions and the app’s availability to the company.

Updated 2026-11-11

Fix an incomplete developer-app authorization request

Check the registered redirect, PKCE method, and request parameters in the app’s OAuth flow.

Updated 2026-11-11

Prevent concurrent OAuth refreshes from revoking a grant

Serialize token refreshes and store the replacement tokens atomically.

Updated 2026-11-11

Activate a webhook endpoint through the signed challenge

A new endpoint does not deliver normal events until its verification succeeds.

Updated 2026-11-11

Restore webhook delivery after rotating its signing secret

Update the receiver and verify the endpoint again with the replacement secret.

Updated 2026-11-11

Handle repeated webhook deliveries without duplicate effects

Use the stable event ID to make your receiver safe for retries.

Updated 2026-11-11