MCP Server Authentication & Setup
Overview
Luciq MCP uses JSON-RPC 2.0 over HTTPS with token-based authentication. Once configured, your IDE can securely list applications, retrieve crash reports, and fetch stack traces all without leaving your development environment.
OAuth-based authentication is currently under development.
Setup Instructions
Luciq MCP uses JSON-RPC 2.0 over HTTPS. We provide token-based authentication requiring two mandatory headers:
Email: Your registered Luciq account email
Token: Your personal access token
How to Get Your Authentication Token
Contact Luciq support team to obtain your authentication token.
Token is tied to your email address and provides access to your applications.
Token provides access control - you can only access applications and data that your account has been granted permissions for.
Server Endpoint
Note: Clustered tenants may have different URLs. Contact Luciq Support for your endpoint.
IDE Configuration
Below are step-by-step setup instructions for supported IDEs, along with example prompts to verify successful connection.
Cursor
Step 1: Configure your MCP server
Open Cursor IDE
Go to "Settings" => "Cursor Settings".
Select "Tools & Integrations" => "New MCP Server"
Create a
.cursor/mcp.jsonfile in your user directory (~/.cursor/mcp.json):
JSON
Note: The server URL will be different for different clusters (single tenants). Contact your Luciq support team to get the correct URL for your specific cluster.
Step 2: Test Connection
Open Cursor IDE.
Use the command palette (
Cmd/Ctrl + Shift + P)Search for "MCP" settings.
Test the connection to verify authentication.
Try listing available tools in the MCP server to validate the connection.
Note: You might need to restart Cursor for the connection to work.
Example Prompt:
“List my applications.” “Show me recent crashes for luciqai.”
Cursor will display a structured list of apps or crash entries directly inside the IDE output panel.
Security & Data Privacy
Luciq MCP is designed with security and data isolation as first principles.
Key Security Measures:
Token-Based Access: Every request requires explicit authentication via your email and unique token.
Scoped Permissions: Tokens are restricted to the apps and environments you’re authorized to access.
Encrypted Transport: All communication occurs over HTTPS (TLS 1.2+).
Best Practices for Teams:
Rotate tokens periodically or after role changes.
Never share tokens in public repositories or internal code.
Contact [email protected] for enterprise security reviews or audits.
Next Steps
Once you’ve confirmed your IDE connection:
Explore the available MCP tools in MCP Tools .
Try real-time prompts to analyze crash data or list applications.
Report feedback or feature requests via [email protected]
Last updated