Tingyun Network MCP Setup

Clients in China#

International Clients#

Before you begin

Obtain the MCP URL, X-Mcp-Client, and authKey from your Tingyun administrator.

Ensure that the client can access the target HTTPS address and supports remote Streamable HTTP.

Verify read-only tools first. Explicit confirmation is required before creating a Synthetic Task, enabling or disabling a task, or initiating an Instant Test.

Support Status and Prerequisites#

Scope note: Directly Supported means only that the client's public configuration format can represent Tingyun's current remote HTTP and request-header requirements. It does not mean that the current tenant, network, permissions, package, or every tool has been verified.

Common Connection Information#

Information required#

Common endpoints#

Qwen / Qwen Code#

Directly supported: In this document, Qwen refers specifically to Qwen Code. It supports remote HTTP MCP services, request headers, and user-level or project-level configuration.

Configuration file#

{
  "mcpServers": {
    "tingyun-network": {
      "httpUrl": "https://<Tingyun-host>/<MCP_ENDPOINT_PATH>",
      "headers": {
        "X-Mcp-Client": "<CLIENT_ID>",
        "authKey": "<AUTH_KEY>"
      },
      "timeout": 60000
    }
  }
}

Verification#

Kimi Code#

Directly supported: Kimi Code supports HTTP MCP services, request headers, enable or disable controls, and timeout configuration.

Configure mcp.json#

{
  "mcpServers": {
    "tingyun-network": {
      "url": "https://<Tingyun-host>/<MCP_ENDPOINT_PATH>",
      "transport": "http",
      "headers": {
        "X-Mcp-Client": "<CLIENT_ID>",
        "authKey": "<AUTH_KEY>"
      },
      "enabled": true,
      "startupTimeoutMs": 20000,
      "toolTimeoutMs": 60000
    }
  }
}

Verification#

Project configuration: Teams may share a project-level configuration template that contains no credentials. Inject the real X-Mcp-Client and authKey through secure local configuration, and do not commit them to Git.

Baidu Comate#

Directly supported: Comate can act as an MCP client and supports Streamable HTTP, remote request headers, and user-level or project-level configuration.

Configuration entry point#

mcp.json example#

{
  "mcpServers": {
    "tingyun-network": {
      "url": "https://<Tingyun-host>/<MCP_ENDPOINT_PATH>",
      "headers": {
        "X-Mcp-Client": "<CLIENT_ID>",
        "authKey": "<AUTH_KEY>"
      },
      "timeout": 60
    }
  }
}

Verification#

Version requirements: MCP prerequisites and mode names in the official Comate documentation may change by version. If the current interface does not include an MCP or Agent entry point, upgrade Comate IDE or the extension and verify account permissions.

TRAE (ByteDance)#

Directly supported: TRAE Agent/Builder supports MCP. You can configure it manually under Settings > MCP and add it to the target Agent.

Setup steps#

Remote MCP configuration example#

{
  "mcpServers": {
    "tingyun-network": {
      "url": "https://<Tingyun-host>/<MCP_ENDPOINT_PATH>",
      "headers": {
        "X-Mcp-Client": "<CLIENT_ID>",
        "authKey": "<AUTH_KEY>"
      }
    }
  }
}

Version check: TRAE publicly documents MCP integration and a manual Raw Config entry point, but validation of remote HTTP fields may vary by version. If the configuration is not recognized, upgrade the client and inspect the MCP output. Do not replace it with an incorrect stdio command.

Verification#

Tencent CodeBuddy#

Directly supported: CodeBuddy IDE supports MCP Market, custom MCP servers, URL and header configuration, and connection status verification.

Setup steps#

~/.codebuddy/mcp.json example#

{
  "mcpServers": {
    "tingyun-network": {
      "type": "http",
      "url": "https://<Tingyun-host>/<MCP_ENDPOINT_PATH>",
      "headers": {
        "X-Mcp-Client": "<CLIENT_ID>",
        "authKey": "<AUTH_KEY>"
      }
    }
  }
}

Verification and notes#

Codex#

Directly supported: Codex CLI, the desktop app, and IDE extensions share the MCP configuration in ~/.codex/config.toml.

Recommended: environment-variable request headers#

[mcp_servers.tingyun_network]
url = "https://<Tingyun-host>/<MCP_ENDPOINT_PATH>"
enabled = true
startup_timeout_sec = 20
tool_timeout_sec = 60
env_http_headers = { "X-Mcp-Client" = "TINGYUN_MCP_CLIENT_ID", "authKey" = "TINGYUN_AUTH_KEY" }

Alternative: static request headers#

[mcp_servers.tingyun_network]
url = "https://<Tingyun-host>/<MCP_ENDPOINT_PATH>"
enabled = true
startup_timeout_sec = 20
tool_timeout_sec = 60
http_headers = { "X-Mcp-Client" = "<CLIENT_ID>", "authKey" = "<AUTH_KEY>" }

Protect the configuration: If static request headers are required, restrict ~/.codex/config.toml so that only the current user can read and write it. Do not create another project-level copy that contains real credentials.

Verification#

Verification, Permissions, and Troubleshooting#

Minimum verification workflow#

Suggested test prompts#

Operation levels#

Mandatory confirmation: Querying Probes does not authorize an Instant Test, and generating a configuration does not authorize task creation. Every operation that changes online state, sends a test to a target, or consumes quota requires separate confirmation.

Common Issues and Troubleshooting#