@muggleai/mcp - npm Package Compare versions

Comparing version 1.0.21 to 1.0.22

package.json

 {
     "name": "@muggleai/mcp",
-    "version": "1.0.21",
+    "version": "1.0.22",
     "description": "Unified MCP server for Muggle AI - Cloud QA and Local Testing tools",
@@ -29,3 +29,3 @@ "type": "module",
     "muggleConfig": {
-        "electronAppVersion": "1.0.8",
+        "electronAppVersion": "1.0.11",
         "downloadBaseUrl": "https://github.com/multiplex-ai/muggle-ai-mcp/releases/download",
@@ -32,0 +32,0 @@ "runtimeTargetDefault": "production",

README.md

@@ -70,2 +70,12 @@ # @muggleai/mcp
 
+### Handling Expired Tokens
+
+Tokens expire after a period of time. When this happens:
+
+1. **Check status**: Run `muggle-mcp status` or call `muggle-remote-auth-status` to see expiration
+2. **Re-authenticate**: Run `muggle-mcp login` or call `muggle-remote-auth-login` to get fresh tokens
+3. **If login fails with "unauthorized_client"**: Check your runtime target configuration (see Troubleshooting)
+
+The MCP server will attempt to auto-refresh tokens when possible, but manual re-authentication may be required if the refresh token has also expired.
+
 ## Available Tools
@@ -159,4 +169,82 @@
 
+## Troubleshooting
+
+### Expired Token Errors
+
+If you see authentication errors like "Not authenticated" or token expiration messages:
+
+1. **Check auth status**:
+   ```bash
+   muggle-mcp status
+   ```
+
+2. **Re-authenticate**:
+   ```bash
+   muggle-mcp login
+   ```
+
+3. **Clear and retry** (if login keeps failing):
+   ```bash
+   muggle-mcp logout
+   muggle-mcp login
+   ```
+
+### "unauthorized_client" Error During Login
+
+This error indicates a mismatch between your Auth0 client configuration and the target environment.
+
+**Cause**: The MCP is configured for one environment (dev/production) but trying to authenticate against another.
+
+**Fix**: Ensure your MCP configuration matches your intended environment by setting the `MUGGLE_MCP_PROMPT_SERVICE_TARGET` environment variable in your MCP config:
+
+**For Production** (`~/.cursor/mcp.json`):
+```json
+{
+  "mcpServers": {
+    "muggle": {
+      "command": "muggle-mcp",
+      "args": ["serve"],
+      "env": {
+        "MUGGLE_MCP_PROMPT_SERVICE_TARGET": "production"
+      }
+    }
+  }
+}
+```
+
+**For Development** (local services):
+```json
+{
+  "mcpServers": {
+    "muggle": {
+      "command": "muggle-mcp",
+      "args": ["serve"],
+      "env": {
+        "MUGGLE_MCP_PROMPT_SERVICE_TARGET": "dev"
+      }
+    }
+  }
+}
+```
+
+After changing the configuration, restart your MCP client (e.g., restart Cursor).
+
+### Credential Files
+
+Credentials are stored in `~/.muggle-ai/`:
+
+| File | Purpose |
+| :--- | :------ |
+| `auth.json` | OAuth tokens (access token, refresh token, expiry) |
+| `credentials.json` | API key for service calls |
+
+If you need to reset authentication completely:
+```bash
+rm ~/.muggle-ai/auth.json
+rm ~/.muggle-ai/credentials.json
+muggle-mcp login
+```
+
 ## License
 
 MIT

Fixed alerts

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Improved metrics

Total package byte prevSize

988196

0.23%

Number of lines in readme file

249

54.66%

Number of medium supply chain risk alerts

12

-7.69%

No dependency changes