Skip to main content
Glama

Discussions

Krusmaster's avatar
Krusmaster18 days ago

Report a bug or a schema that came out wrong Open an issue on GitHub. For a plan that came out wrong, include the table and column names involved (anonymised if you need to), the key or relationship Krusgraph proposed or missed, and the rule it gave. Never post customer data or real workspace ids. The most common first errors A tool that cannot finish answers with a kind. These are the ones people meet first: sign_in: the connector’s sign-in has expired or was never completed. In Claude, disconnect and reconnect Krusgraph, then finish the Microsoft sign-in. consent: your Entra admin hasn’t approved Krusgraph yet, or the tool needs a permission the hosted app doesn’t have. Send your admin the consent link on Connect to Claude. no_access: the workspace or item isn’t shared with you. Ask its owner for Viewer to read and plan, or Contributor to create. capacity: the workspace has no active Fabric capacity. Assign or resume one under Workspace settings → License info. schema_not_found: the schema has no tables for this sign-in. A lakehouse without schemas keeps its tables in dbo. The exact steps for each are in the docs: First-time errors.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.