Implementation test plan

Before you start

Set up two test tenants with different server addresses and WorkOS organizations.
Prepare one test account whose MCP permissions you can change between tests.
Make sure you can turn MCP on and off for each test tenant without changing unrelated access.

Covers AC-1, AC-3 and AC-6.

Turn MCP on for the first test tenant and give your account read-only MCP access (mcp:read).
Follow your chosen MCP client's setup instructions and save the connection. Saving alone must not sign you in.
Sign in through WorkOS. Check that the connection belongs to the intended tenant and environment.
Cancel sign-in. Check that access is still unavailable and you can try signing in again.
After successful sign-in, start a new chat session and send try hello_read. Check that the tool returns Hello..

Check the tool replies

Covers the visible tool replies in AC-4 and AC-6.

Give your account MCP read and write access.
Send try hello_read. Check that the reply contains the greeting Hello..
Send try hello_write. Check that the reply confirms MCP write permission and says no data was changed.
Repeat both calls. Check that the replies convey the same results, even if the client's wording varies.

Check who can use each tool

Covers AC-2 and AC-3, plus permission changes and tenant disablement in AC-5. Use the same account and chat with each permission combination below, letting permission changes take effect before starting the next case. Check the tool list and try the tools in the chat.

Turn MCP on for the first tenant.
Give your account MCP read and write access. Check that both tools work.
Remove write permission, leaving read access only. Check that hello_read is listed and works, while hello_write is hidden.
Send try hello_write with read-only access. Check that the client reports the tool as unavailable or access as denied.
Remove read permission too. With no MCP permissions, check that neither tool can be listed or used.
Give your account write permission without read permission. Check that neither tool can be listed or used.
Restore both permissions. Check that both tools are listed and work again. The write reply must say no data was changed.
Turn MCP off for the tenant and repeat all four permission combinations. Check that neither tool can be used.
Turn MCP back on. Check that users regain only the access their permissions allow.

See the permission and error rules for the required server status codes and messages.

Check errors and recovery in the client

Covers the client experience in AC-1, AC-5 and AC-6. The client experiments show examples; wording may vary.

If your client offers a sign-out option for the MCP connection, use it. Send try hello_read and check that the client reports unavailable access rather than success.
Start signing in again from the saved MCP connection. Cancel, then check that you can try signing in again.
Complete WorkOS sign-in. Check whether the client retries the failed request itself. If needed, send try hello_read again and check that the greeting works.
Review the permission denials from the earlier tests. Check that they explain the missing access, point to an administrator and do not repeatedly ask you to sign in.
Stop the test MCP service and send try hello_read. Check that the client reports a connection problem rather than success.
Start the service again and send try hello_read in the same chat. If the tool remains unavailable, try a new chat and check whether it works there.

Check operation and existing features

Covers AC-3 and AC-6. See the automated identity and tenant checks for server regression coverage.