Skip to main content

MCP support

Use https://mcp.griff.run/mcp in your client. Start with the connection guide.

If connection fails, record the client name and version, UTC time, the step that failed, and the HTTP status or sanitized error message. Never send a workspace access key, OAuth token, authorization code, or complete client registration ID.

Common checks:

  • A 401 from the MCP endpoint before sign-in is expected and should point the client to OAuth discovery.
  • An invalid scope or wrong resource is rejected intentionally.
  • Revoked credentials must be replaced through the approved workspace process.
  • If a client cached connect.griff.run, remove and re-add the connection using mcp.griff.run.

For operator help, use the support channel named in your GRIFFai service agreement.