Skip to main content

AI Assistant Issues

Solving problems with AI assistants connecting to Wellpipe.

Claude Desktop​

Tools Icon Not Appearing​

The hammer/wrench icon should appear in Claude Desktop when MCP servers are configured.

Checklist:

  1. ✅ Config file exists and is valid JSON
  2. ✅ File is in the correct location
  3. ✅ Claude Desktop was fully restarted (Cmd+Q)
  4. ✅ API key is correct

Config file locations:

  • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Validate JSON:

# Mac/Linux
cat ~/Library/Application\ Support/Claude/claude_desktop_config.json | python -m json.tool

# Or use an online JSON validator

"Server not found" Errors​

MCP server can't be reached.

Causes:

  1. npx not available - Install Node.js
  2. Network issue - Check internet connection
  3. Firewall - Allow Node.js network access

Fix:

# Verify Node.js is installed
node --version
npx --version

# Test the MCP connection manually (optional)
npx mcp-remote https://wellpipe.io/api/mcp/auth --header "Authorization: Bearer YOUR_KEY"

Wrong API Key​

Symptoms: Auth errors or "unauthorized" messages

Fix:

  1. Get your API key from app.wellpipe.io
  2. Update claude_desktop_config.json
  3. Restart Claude Desktop

Common mistakes:

  • Extra spaces before/after the key
  • Using old/regenerated key
  • Missing "Bearer " prefix in header

Config File Syntax Errors​

Symptoms: Claude doesn't load any MCP servers

Common issues:

// WRONG - trailing comma
{
  "mcpServers": {
    "wellpipe": { ... },  // ← trailing comma breaks JSON
  }
}

// CORRECT
{
  "mcpServers": {
    "wellpipe": { ... }
  }
}

ChatGPT (Custom GPT)​

Action Not Working​

Symptoms: GPT doesn't call the Wellpipe API

Checklist:

  1. ✅ OpenAPI schema imported correctly
  2. ✅ Authentication is set to "API Key" + "Bearer"
  3. ✅ API key is entered correctly
  4. ✅ GPT instructions mention using the action

Fix instructions: Update your GPT instructions to be more directive:

When asked about sleep, recovery, or workouts, ALWAYS use the getHealthData action first to fetch real data. Never respond about health data without calling the API.

"No such endpoint" or Schema Errors​

Symptoms: Action fails with endpoint errors

Fix:

  1. Delete the existing action
  2. Create new action
  3. Import from URL: https://wellpipe.io/openapi.json
  4. Reconfigure authentication

Authentication Errors​

Symptoms: 401 or "unauthorized" errors

Checklist:

  1. Authentication type: API Key
  2. Auth Type: Bearer
  3. API key pasted correctly (no extra spaces)
  4. Key is valid (not regenerated since setup)

GPT Doesn't Use Action​

Symptoms: GPT responds without fetching data, or makes up data

Causes:

  • Vague instructions
  • GPT decides it can answer without data

Fix: Be explicit in your prompt:

  • ❌ "How did I sleep?"
  • ✅ "Use the Wellpipe API to get my sleep data from last night"

Or update GPT instructions to always call the action first.

Claude Web / REST API​

"Can't access external URLs"​

Symptoms: Claude refuses to make HTTP requests

Solutions:

  1. Rephrase: "Please make an HTTP GET request to this URL..."
  2. Be explicit about the full URL and headers
  3. Try: "Fetch the contents from..."

Request Format Errors​

Make sure your prompt includes:

Fetch my health data from this API:

GET https://wellpipe.io/api/v1/health?type=summary&days=7
Authorization: Bearer YOUR_API_KEY

Common mistakes:

  • Missing the Authorization header
  • Using POST instead of GET
  • Malformed URL

Response Parsing Issues​

If Claude has trouble parsing the response:

  1. Ask for specific fields: "What's my recovery score from that data?"
  2. Request summary: "Give me the key highlights"
  3. Ask for clarification: "Can you show me the sleep duration?"

Mobile Apps​

ChatGPT/Claude Mobile​

Same as web versions - use REST API prompts.

Tips for mobile:

  • Save your API prompt as a note to copy/paste
  • Create text shortcuts for common queries
  • Keep prompts short for easier typing

iOS Shortcuts Errors​

"Couldn't connect to server"

  • Check URL is correct
  • Verify Authorization header format
  • Test with curl first

Empty response

  • Check API key is valid
  • Try a different type parameter
  • Reduce days parameter

General Debugging​

Check Connection First​

Before debugging AI issues:

  1. Go to app.wellpipe.io
  2. Verify WHOOP shows "Connected"
  3. Check token hasn't expired
  4. View usage stats (not rate limited)

Test API Directly​

curl "https://wellpipe.io/api/v1/health?type=summary&days=7" \
  -H "Authorization: Bearer YOUR_API_KEY"

If this works, the issue is in the AI assistant configuration. If this fails, check your connection in the dashboard.