Skip to main content

CodeBuddy Usage

This chapter uses CodeBuddy as the primary example. Other MCP-compatible clients such as Cursor and Claude Desktop use the same configuration fields; brief notes are at the end.

Complete the mcp.json configuration first. Open mcp.json Configuration, copy the full JSON for your CrashSight site (China or international), replace csk_xxx with your real API Key, and save it. CodeBuddy cannot connect to CrashSight MCP until this configuration is in place.

1 CodeBuddy​

1.1 Verify the connection​

After mcp.json is configured, restart CodeBuddy or refresh the MCP Server list. When the connection succeeds, you should see a server named crashsight and CrashSight tools such as who_am_i, get_app_info_list, and advanced_issue_search.

Try a connectivity check in chat:

  • "Who is my current CrashSight account?"
  • "List the CrashSight apps I can access"

The client should call who_am_i and get_app_info_list. If you get your account info and app list back, CodeBuddy is connected to CrashSight MCP.

1.2 Typical prompts​

After the connection works, query in natural language, for example:

  • "Show unhandled crash issues for app {appId} in the last 7 days"
  • "What is the latest stack for this Issue link?"
  • "Compare yesterday's and today's crash trend for this app"

Replace {appId} with a real app ID, or ask the assistant to call get_app_info_list first. See Tool Reference for tool details.

2 Other MCP-compatible clients​

Complete mcp.json Configuration first as well. The configuration shape is the same as CodeBuddy: mcpServers → server name → url plus headers.X-CSMCP-API-KEY. Replace csk_xxx with your real key and use the MCP URL that matches that key.

2.1 Cursor​

Add the completed mcp.json configuration to Cursor MCP settings. Then confirm crashsight is connected. Some Cursor versions omit the type field.

2.2 Claude Desktop​

Add the completed mcp.json configuration to the Claude Desktop MCP configuration (mcpServers). Restart Claude Desktop and confirm CrashSight tools appear.

If a client does not yet support remote HTTP MCP, see that client's docs for Streamable HTTP / HTTP MCP. CrashSight MCP does not provide a local stdio process; connect over HTTP.