HomeDocumentationAPI Reference
Getting StartedAPI ReferenceDashboardHelp Center
Documentation

Luciq MCP Server

📘

Beta Availability Notice

The Luciq MCP Server is currently in Private Beta - Early Access.
It’s still under active development, and we’re collecting early feedback from selected customers before general release.
You may experience incomplete functionality or changes between versions.
If you’d like to join the beta or share feedback, contact [email protected].

Connect your AI IDE directly to Luciq’s mobile observability data.

The Luciq MCP (Model Context Protocol) Server provides a standardized, secure interface that allows any compatible AI model or IDE, such as Cursor, Claude Code, or VS Code MCP clients, to access crash data, analytics, and debugging insights from Luciq.

Use natural language to query and explore your app’s health directly inside your IDE:

“List my Android apps”
“Show me production crashes from the last week”
“Get crash #42 details”


Overview

Luciq MCP follows the authenticated remote MCP spec, enabling AI-native tools to connect safely to your workspace.

The server exposes tools for:

  • Listing applications
  • Fetching crash reports
  • Retrieving detailed crash traces
  • Discovering crash patterns

What is MCP?

Model Context Protocol (MCP) is an open standard introduced by Anthropic. It defines a secure, language-agnostic way for AI tools (like Claude or Cursor) to connect to external data sources and APIs.

In simple terms: MCP allows your AI IDE to “talk to Luciq”, requesting crash logs, analytics, or version data directly from your app’s workspace, using standardized JSON-RPC calls.

Luciq’s MCP Server brings this capability to mobile observability, making it the first MCP integration designed specifically for mobile debugging and release management.

Why MCP?

  • Standardized Interface. Works natively across all MCP-compatible IDEs
  • AI-Ready. Lets LLM-powered assistants reason over Luciq data.
  • Simple Integration. One configuration file, no SDKs required.
  • Secure by Design. Token-based access scoped to your workspace

Quick Start

Get your first response in under two minutes.

Prerequisites

  • A Luciq account
  • Your registered email
  • A personal access token (request via [email protected])
ToolWhat it DoesExample Prompt
listApplicationsLists all apps connected to your workspace"List my Android apps."
listCrashesRetrieves crash reports for a specific app or environment"Show production crashes for luciqai."
crashDetailsDisplays stack trace and metadata for a crash"Get details for crash #42."
crashPatternsAggregates crash data by device, OS, or version"Show crash patterns for crash #5 grouped by devices."

Next Steps


FAQs

Why am I seeing “App not found”?
Your token may not have permission for that app or mode.
Check with your Luciq admin.

Can I rotate tokens?
Yes — contact [email protected] to regenerate.

Does Luciq support OAuth 2.1?
Coming soon. Current auth is token-based via headers.