Zoho Apptics MCP

- Open Windsurf settings (⌘ +,).
- Go to the Cascade tab and click Add Server.
- Select Add custom server +.
- Add the following JSON configuration, replacing the placeholder key with your MCP key from below.

Note: Treat your MCP server key like a password! It can trigger tools linked to this server and access your data.

Use tools directly inside Visual Studio Code with Zoho Apptics MCP. Allow your AI assistant to perform real-world actions through a secure, simple connection—without leaving your coding workspace.

Important: You must have GitHub Copilot enabled and set to Agent mode in Visual Studio Code for Zoho Apptics MCP to function correctly.

- Open the Visual Studio Code Command Palette (⇧ + ⌘ + P on Mac, Ctrl + Shift + P on Windows).
- Type "MCP: Add Server..." and press Enter.
- Choose "HTTP (HTTP or Server-Sent Events)" and press Enter.
- Paste your MCP key from below into the "Server Key" field and press Enter.
- Provide a server name and press Enter.
- Make sure GitHub Copilot is set to Agent mode.
- Ask GitHub Copilot to use tools from your Zoho Apptics MCP server!

Caution: Treat your MCP server key like a password! It can trigger tools linked to your server and access sensitive data.

If your AI agent, IDE, or automation tool supports the Model Context Protocol, paste the URL from above and you're done. No special setup needed beyond what your client requires.
- {
- "mcpServers": {
- "ZohoMCP": {
- "command": "npx",
- "args":
- "mcp-remote",
- "[https://suptest-122752501.testzohomcp.com/mcp/3da990c773069d237627c05d7e5aa20b/message",
- "--transport",
- "http-only"
- ]
- }
- }
- }

Warning:Treat this URL like a password. It can trigger tools linked to your account and access your data. Don't paste it into public repos, shared docs, or anywhere others can read it.

Zoho MCP uses HTTP (Streamable HTTP) transport. Select this if your client asks you to choose: HTTP / Streamable HTTP

If your client accepts a JSON config file (common in IDE-based agents), paste this block:
- Open your client's MCP or integrations settings
- Add a new MCP server — look for Add server, New connection, or a mcp.json config file
- Set transport to HTTP or Streamable HTTP
- Paste the MCP URL from above into the server URL field
- Save and enable Agent mode or equivalent in your client

Note:Clients known to work with Zoho MCP include Zed, Continue, Cline, n8n, and others that support Streamable HTTP transport. If yours isn't listed and the steps above don't work, check your client's MCP documentation or write to us [email protected].
- Node.js 18 or more.
- Zoho Apptics OAuth credentials, i.e., client ID, client secret, and a refresh token with access to Apptics APIs.

To configure Zoho Apptics local MCP server, you need to provide OAuth credentials (client id, client secret, and refresh token) as environment variables.
-

Create a new self-client application fromZoho API console.

curl -X POST "https://accounts.zoho.com/oauth/v2/token" \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "code=YOUR_SELF_CLIENT_CODE" \ -d "client_id=YOUR_CLIENT_ID" \ -d "client_secret=YOUR_CLIENT_SECRET" \ -d "grant_type=authorization_code"

{ "mcpServers": { "zoho-apptics": { "command": "npx", "args": ["@zoho_apptics/apptics-mcp"], "env": { "APPTICS_CLIENT_ID": "your_client_id", "APPTICS_CLIENT_SECRET": "your_client_secret", "APPTICS_REFRESH_TOKEN": "your_refresh_token" } } } }

The MCP integration provides access to the core capabilities of Apptics:

Retrieves application details for the dashboard view such as app name, bundle ID, platform, and status.
- Total affected users (usercount)
- Unique crash issues (issuecount)
- Total crash events (crashecount)
- Affected devices (devicecount)
- Crash-free users percentage (crashfreeusers)
- Number of crashes per day (crashcount)
- Unique devices affected per day (devicecount/deviceschart)
- Unique users affected per day (usercount/userschart)
- Unique crashes per day (issuecount/issueschart)

Timestamps are returned as UNIX epoch time in milliseconds.

Retrieves detailed crash metadata and diagnostic trace for a specific crash event. Includes:
- Device Model and OS version details
- App context (AppVersion, AppReleaseVersion)
- Session metadata (SessionStartTime, UserID, DeviceID, NetworkStatus)
- Crash diagnostic info (Exception, IssueName, Message, CustomProperties)

Similar to getCrashesByDate but allows timezone-based time interval grouping. The response provides platform-specific daily crash metrics adjusted to the specified timezone.

Retrieves date-wise crash count statistics for a specific crash issue identified by its unique ID. Useful for tracking the frequency trend of a particular crash over time.

getCrashCountByDateWithTimezoneForUnique

Retrieves date-wise crash count statistics with timezone support for a specific crash issue. Combines per-issue filtering with timezone-adjusted date grouping.

Retrieves device model distribution data for a specific crash issue. Shows which device models are most affected. It is useful for identifying hardware-specific issues.

Retrieves OS version distribution data for a specific crash issue. Shows which OS versions are most affected. It is useful for identifying OS-specific regressions.

Retrieves the list of affected devices for a specific crash issue. Shows individual device details that experienced this crash. It is useful for support and debugging workflows.

Retrieves time-series chart data for crashes and exceptions.
- Use group=fatal to view crash trends (daily crash counts over time).
- Use group=nonfatal or group=error for handled-exception and error trends.

Retrieves the total count of crashes or exceptions for a specific group:
- Total crash count (fatal errors or app-terminating failures)
- Total handled/non-fatal exceptions count (non-fatal errors)
- Logged errors count (JS errors)

Retrieves the V2 crash and exception report list. When group=fatal, returns the crash report list — each row represents a unique crash issue with its issue name, exception signature, affected app versions, total crash count, and affected user/device counts.

Retrieves the count of unique occurrences for a specific crash or exception issue. Use exceptionGroup=fatal to count crash occurrences.

Retrieves the full stack trace for a specific crash or exception. The symbolicated trace includes method calls, file names, line numbers, and thread information and acts as a primary debugging tool.

Retrieves time-series trend data for a specific crash or exception issue. Shows how occurrence frequency changes over time. It is useful for monitoring regressions after releases.

Retrieves device-model and OS-version distribution data for a specific crash or exception issue. It is useful for determining if a crash is hardware-specific or OS-specific.

Retrieves the list of individual devices affected by a specific crash or exception. Returns per-device records including device model, OS version, app version, and crash timestamps.

Retrieves ANR statistics grouped by date. ANRs are Android-specific 'App Not Responding' errors that occur when the main thread is blocked for too long.

Retrieves a summarized view of ANR statistics including total ANR count, affected users, devices, and issue counts.
- Logical category/module (event group name)
- Name of the tracked event (event name)
- Number of occurrences (events count)

Retrieves event activity grouped by date and platform. Each event entry includes:
- Name of the event (event name)
- Number of occurrences (event count)
- Epoch timestamp in milliseconds (date)

Searches for specific custom events from the BDaaS data store. Allows filtering by event name, group name, platform, and date range.

Retrieves retention statistics based on screen views. Analyzes how users return to specific screens over time at day, week, or month granularity.

Retrieves session count statistics aggregated by one or two grouping dimensions such as date, platform, app version, country, device type).

Retrieves remote logging statistics. Remote logs are diagnostic logs sent from devices that can be filtered by function name, log message, severity level, device model, device ID, and user.

- Open a new chat.
- Choose Search and tools.
- Pick the Zoho Apptics MCP connection.
- Select the tools you’d like to use in the chat.
- Ask Claude to perform actions using them!

Use tools from Zoho Apptics MCP directly inside Cursor IDE. Enable your AI assistant to perform real-world actions securely—without leaving your coding workspace.
- {
- "mcpServers": {
- "ZohoMCP": {
- "url": "YOUR_INTEGRATION_URL"
- }
- }
- }

You can first try clicking the "Add to Cursor" button for automatic setup. If manual installation is needed, follow these steps:
- Add Zoho Apptics MCP Server.
- Open Cursor settings (⇧ + ⌘ + J).
- Go to the MCP Tools tab and click New MCP Server.
- Copy and paste the following JSON configuration below, then save it using CMD + S or CTRL + S.
- Activate Agent Mode.
- Make sure the chat is set to Agent mode to access Zoho Apptics MCP tools within Cursor.

Important: Treat your MCP server key like a password. It can trigger tools connected to your account and access sensitive information.