Skip to content
Engram Docs

Troubleshooting

Endpoints

Section titled “Endpoints”
  • Cloud: https://app.engram.page/api/mcp
  • Self-host: https://your-engram-host/api/mcp

”Failed to connect”

Section titled “”Failed to connect””
  • Wrong URL — the MCP endpoint lives at /api/mcp (see endpoints above). The bare host (no path) is not the MCP endpoint and will return 404.
  • Self-host TLS — the MCP endpoint must be HTTPS. Plain HTTP is rejected by clients per OAuth 2.1.
  • Backend not reachable — confirm you can hit /api/health directly. If that fails, MCP can’t possibly work.

”Authorization failed”

Section titled “”Authorization failed””
  • Account not active — log in to app.engram.page and check your subscription is in good standing.
  • Onboarding not complete — Engram requires Terms acceptance before vault endpoints (including MCP) are usable.
  • Rate-limited during OAuth — wait a minute and retry.

Claude finds no notes

Section titled “Claude finds no notes”
  • Confirm the vault has actually been synced from Obsidian — check the Sync Center and app.engram.page.
  • Confirm the OAuth token actually carries the mcp scope — re-add the Connector if you skipped authorization on first install.
  • Try a more specific query — semantic search returns top-K, so vague queries on a big vault may not surface what you expect.

”Token expired”

Section titled “”Token expired””

OAuth tokens have a finite lifetime. Most clients handle refresh automatically — try the operation again. If the failure persists, remove and re-add the Connector.

Where to look for more info

Section titled “Where to look for more info”
  • Server-side logs — for self-host, see Self-Host
  • Client-side logs — Claude Desktop → Help → Open developer console
  • File issues at engram-app/engram