Troubleshooting
Endpoints
Section titled “Endpoints”https://mcp.engram.page”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/healthdirectly. If that fails, MCP can’t possibly work.
”Authorization failed”
Section titled “”Authorization failed””- Account not active. Log in to
app.engram.pageand 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
mcpscope; 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