Connect a client and verify

Connect an AI client, test one read-only tool, and confirm the activity in your Stackyapper workspace. This closes the onboarding loop with proof that the whole path works end to end.

Connect the client

The general flow is the same for every AI client:

Add the Stackyapper URL to your client
ChatGPT uses https://mcp.stackyapper.dev; every other client uses https://mcp.stackyapper.dev/mcp. Client-specific menus and field names are covered in the guides for ChatGPT, Claude, Codex, Microsoft Copilot Studio, and other AI clients.
Complete OAuth authorization
When the client opens the Stackyapper sign-in, authenticate with the same company identity you use in the portal.
Approve the connection
Read the workspace name on the Stackyapper consent page and confirm it is the workspace containing the app you just connected. Approve, then return to the AI client.

Stop if the consent page shows the wrong workspace. Return to the portal, select the intended workspace, and start the client connection again.

Test a small read-only request

Adapt this request to the app and record selected during preparation:

1234Using Stackyapper, find a read-only tool for [app] that can list [record type].
Retrieve no more than five records. Do not create, update, delete, execute, or
otherwise change provider data. Tell me which Stackyapper tool you used and
whether the request succeeded.

For example, with a PSA connected the prompt might be "Using Stackyapper, find a read-only tool for ConnectWise that can list service tickets. Retrieve no more than five records…" An illustrative successful response — your tickets and wording will differ:

123I used a Stackyapper tool to search tickets and retrieved 5 open service
tickets: #4021 "Printer offline – Acme", #4019 "New starter laptop", …
The request succeeded and no data was changed.

The exact tool depends on the connected app and your grants. A successful result should contain recognizable provider data and should not request confirmation for a write operation.

Verify the audit record

An owner or administrator should:

Open Audit
In the Stackyapper portal, confirm the same workspace is selected and open Audit.
Find the call
Locate the recent event using its time, app, tool, user, client, or successful status.
Confirm the activity
Confirm that the app, tool, user, AI client, result, and approximate time match the test.

Audit records show how Stackyapper was used — identity, app, tool, and outcome — without storing the tool arguments or the data returned by the connected app.

If the test fails

Result	Check
Client cannot connect	Confirm the client-specific Stackyapper URL and repeat OAuth.
Wrong workspace appears	Select the intended workspace in the portal and reconnect the client.
App is missing	Confirm app availability and workspace enablement.
Tool is missing	Confirm the user or group has a grant for that read tool.
App needs attention	Reconnect or repair the provider credential.
Permission denied on a tool you expected to work	Check the user's grants and their groups' grants for that tool, then look for a restriction that overrides them.
Permission denied on a risky or write operation	Check the workspace risk ceiling and app policy; onboarding grants should be read-only, so a denial here may be working as intended.
Provider error	Confirm the provider URL, region, scopes, credential, and service availability.

See Troubleshooting for additional connection guidance.

Completion checklist

The client is connected to the intended Stackyapper workspace.
The read returned expected provider data.
No provider data was changed.
The matching successful audit event is visible.
The user has no unnecessary tool grants.

Invite your team

Move from a single-user test to controlled team access.