1.
You have obtained a valid authkey from a Tingyun Network administrator. <AUTH_KEY> in this document is only a credential placeholder. Replace it with the actual value during configuration and configure it as the authentication HTTP request header for MCP requests as described below.
Image showing where to obtain the authkey

2.
You have identified the MCP services required for your business: Alerts, Instant Testing, or Synthetic Monitoring task management. Each service has a different MCP Server endpoint and toolset and must be configured separately.
3.
Your AI Agent supports remote MCP connections over Streamable HTTP and allows custom HTTP request headers to be configured for an MCP Server so that the authkey can be passed.
4.
The network used by the AI Agent can access the corresponding Tingyun Network MCP service endpoint over HTTPS.
JSON not recognized: Check the braces, commas, field names, and transport type. Replace AUTH_KEY with the actual authorization code. Do not leave the placeholder or HTML entity encoding in the configuration.
Tools not visible: Confirm that the Alert MCP Server endpoint is correct, the Alert MCP service is enabled, and it has been added to the target AI Agent. After changing the configuration, start a new session to load the latest configuration.
403: Check whether the authkey is missing, expired, or copied incorrectly.
404 / 405: Confirm that the client is using Streamable HTTP rather than the legacy SSE transport.
Connection timeout: Check the proxy, DNS, TLS certificate, and corporate network allowlist, then increase the startup timeout as appropriate.