Before you begin, keep your onboarding handoff available. You need the assigned endpoint, the supported AI application and the authentication details delivered securely by DigLab.
Step 1 Confirm your setup#
Check that the organisation and service account named in the handoff are yours. Read the list of approved tools and any limits. If the handoff names a particular workspace or brand, use that exact workspace during your test.
Do not replace your assigned endpoint with the platform home address. The home page, an administrator login and an MCP endpoint serve different purposes.
Step 2 Add the connection#
Open the MCP or connector settings in the agreed AI application. Add a remote HTTP connection using the exact endpoint you received. For the managed API-key setup, enter the assigned key in the client's secure authentication field using the header name supplied in the handoff. The verified header for this setup is X-API-Key.
Use connect your AI client for the complete connection checklist. If the application only offers OAuth, read compatibility before continuing.
Step 3 Inspect the tools#
Ask your AI application:
List the tools available through my MCP DigLab connection.
Explain what each tool does. Do not run any tools yet.Compare the names and purposes with the handoff. Unexpected access or a missing service should be investigated before doing business work.
Step 4 Run the agreed read-only test#
Use the harmless test selected during onboarding. For example, retrieve a single approved test record or read a service status. Ask the AI to show the account or workspace context when the tool exposes it.
Use the approved read-only test from my onboarding handoff.
Show the tool used, the account context and the result.
Do not send, publish, delete or update anything.Step 5 Check the result#
Confirm that the record belongs to your organisation and that the returned values match the expected source. You are ready for the agreed workflow when connection, tool discovery and the read-only result all pass. Keep your handoff and secure credential reference; do not save a raw key in a shared checklist.