mcp.json Configuration
CrashSight MCP uses Streamable HTTP. Add the following mcp.json entry to your MCP-compatible client and replace csk_xxx with the real key from MCP Token Management.
Choose the configuration that matches the CrashSight site you use. Do not mix URLs and keys from different environments.
1 China environment
Use this if your console is https://crashsight.qq.com. Save the JSON to the CodeBuddy user-level file ~/.codebuddy/.mcp.json (if the file already exists, merge the crashsight block into mcpServers):
{
"mcpServers": {
"crashsight": {
"type": "http",
"url": "https://crashsight.qq.com/mcp",
"headers": {
"X-CSMCP-API-KEY": "csk_xxx"
}
}
}
}
- MCP Server:
https://crashsight.qq.com/mcp - Get a key: https://crashsight.qq.com/account/profile?tag=mcpToken
2 International environment
Use this if your console is https://crashsight.wetest.net. The layout is the same as the China configuration; only the domain changes:
{
"mcpServers": {
"crashsight": {
"type": "http",
"url": "https://crashsight.wetest.net/mcp",
"headers": {
"X-CSMCP-API-KEY": "csk_xxx"
}
}
}
}
- MCP Server:
https://crashsight.wetest.net/mcp - Get a key: https://crashsight.wetest.net/account/profile?tag=mcpToken
3 Field reference
| Field | Description |
|---|---|
mcpServers.crashsight | MCP Server name. You can rename it to match your client |
type | Always "http" (Streamable HTTP) |
url | CrashSight MCP endpoint. Must match the environment where the key was created |
headers.X-CSMCP-API-KEY | Your personal API Key. Replace csk_xxx with the real token |
After saving, follow CodeBuddy Usage to finish the setup. Some clients do not require the type field; url and headers are enough.