Skip to main content

​
Troubleshooting

​
MCP connection issues

Symptom: Your AI tool can’t connect to BaseLayer, or tool calls fail. Fix:
  1. If using remote MCP (Claude.ai, ChatGPT): check your internet connection and try re-authorizing the OAuth connection
  2. If using IDE MCP (Cursor, Windsurf, etc.): verify your MCP configuration file has the correct URL (https://api.baselayer.id/mcp)
  3. Try removing and re-adding the BaseLayer MCP integration
  4. Start a new conversation (MCP tools may not appear in existing ones)

​
Chrome extension not capturing

Symptom: Conversations aren’t appearing in your memory. Fix:
  1. Click the BaseLayer extension icon and check the status dot
  2. Green dot: capturing normally
  3. Gray dot: you’re not on a supported site (Claude, ChatGPT, Gemini, OpenRouter, Open WebUI)
  4. Red dot: error. Try signing out and back in from the extension popup
  5. Refresh the AI page and try again

​
No entities appearing

Symptom: You’ve been using BaseLayer but no entities are showing up. Fix:
  1. Check that your conversations are being captured (look for recent activity in the desktop app)
  2. Dream engine processing takes time: Pro users ~2 minutes, Free tier up to an hour
  3. Try asking an AI connected via MCP: “What do you know about me?” to verify the connection

​
Dream engine not processing

Symptom: Conversations are captured but no entities are being extracted. Fix:
  1. Open the desktop app and check Settings for dream engine status
  2. On the Free tier, processing runs every 2 hours. Wait for the next cycle
  3. On Pro, processing should happen within a few minutes. If it’s delayed, try restarting the desktop app

​
MCP tools not appearing in Claude.ai

Symptom: You connected BaseLayer but Claude doesn’t use the tools. Fix:
  1. Go to Settings → Integrations in Claude.ai and verify BaseLayer is listed
  2. Try removing and re-adding the integration
  3. Start a new conversation (tools may not appear in existing ones)
  4. Try explicitly asking: “Use BaseLayer to search for information about my projects”

​
Slow search results

Symptom: Queries take a long time to return. Fix:
  • Use ask_question for direct answers (most efficient)
  • Use memory_search with depth: "distilled" for faster results
  • For get_entity_relations, use the query parameter to filter rather than retrieving all edges