SUPPORT

Identify where the connection stops.

Check the endpoint first, then authentication, permissions and the result reported by your client.

The client cannot connect

Compare the configured URL with the endpoint supplied for your workspace.
Check connectivity from the machine or container that runs the MCP client.
Inspect the client's server output for a timeout, network error or unsupported transport.
Keep certificate verification enabled; resolve the certificate or hostname issue before retrying.

Authentication and resource errors

Observation	What to check
401 / authentication required	The connection identity and the current authentication configuration.
403 / access denied	The project, environment and permissions assigned to this connection.
404 / endpoint not found	The full URL, including any path supplied by your administrator.
Empty resource list	The selected workspace, environment and available resource scope.
Unknown method or tool	The capabilities actually discovered by your client.
429 / rate limited	The response's retry guidance; avoid repeated immediate retries.

Give your administrator useful context

Include the date, time zone, client version, server address, environment and exact error code. Describe the operation you expected. Remove credentials and secret resource contents from logs and screenshots before sharing them.

Connection report template

Time and time zone: <time>
MCP client and version: <client>
Server address: https://mcp.myvaultdesk.com
Environment: <environment>
Operation: <operation>
Error code: <code>
Expected result: <description>

TEXT

Review the connection steps

Compare your setup with the client configuration guide.

Read the guide