Skip to main content
This page covers Graphify, the hosted product at app.graphify.com. Each section heading uses the error text you see, so you can search for it. Every API error has the same shape. Include the correlationId when you contact support:
Error response

​
Sign-in and MCP OAuth errors

​
MCP client shows “Needs login” or “needs authentication”

Your client hasn’t finished the one-time browser sign-in. Graphify answers a request with no token with 401 and a WWW-Authenticate header, which starts the sign-in.
  • Claude Code: run /mcp, select graphify, and choose Authenticate.
  • Codex: run codex mcp login graphify.
  • Cursor: select Needs login next to the server.
See Hosted MCP for how sign-in works.

​
invalid_grant: “Refresh token superseded; retry the login.”

Several agent sessions shared one stored login and refreshed at the same time. Only one refresh wins. Sign in again from the client that failed.

​
invalid_grant: “Refresh token reuse detected.” or “Refresh token expired.”

The stored login is no longer valid. Sign out of the server in your client, then sign in again. Other invalid_grant messages, such as “Authorization code expired.” or “PKCE verification failed.”, also mean you should start the sign-in again.

​
invalid_client_metadata: “Only public clients (auth method ‘none’) are supported.”

Your client tried to register with a client secret. Graphify supports public OAuth clients only. Use the client’s standard remote MCP setup, or the mcp-remote bridge.

​
429 on sign-in

Too many token refreshes for one login in a minute. The response includes Retry-After. Wait that long, then retry.

​
”Your session expired. Signing you back in…”

The console’s session ended. The console signs you in again on its own. If it keeps happening, sign out and sign in again.

​
MCP workspace errors

​
no_workspace: “No workspace is selected for this agent.”

You belong to more than one workspace and haven’t picked one. The message lists your workspaces. Ask your agent to run set_workspace with one handle. set_workspace changes which workspace the session reads from.

​
workspace_access_revoked

You were removed from the bound workspace, or lost access. Run list_workspaces and pick another.

​
mcp_session_required: “set_workspace can only run inside an established MCP session.”

Reconnect the server in your client, then run set_workspace again.

​
list_repositories is empty

You’re in a workspace with no indexed repositories, or the repository is still indexing. Check the workspace with list_workspaces, and check indexing in the console.

​
429 rate_limited: “Too many requests. Please slow down.”

You went over a default per-minute limit: Back off and retry with exponential delay and jitter. The usual cause is an agent calling Graphify in a tight loop. In CI, treat a 429 from test impact as “run the full suite”. See Rate limits.

​
Indexing failed or stuck

​
”Taking longer than usual. Still indexing.”

Large repositories take longer. The build is still running. Wait, and keep using the last published graph in the meantime.

​
”Indexing failed”

Open the repository in the console and select Retry indexing. For a combined graph, the message is “Your graph couldn’t finish building” with a Retry build button.

​
”Nothing to show yet”

No code was found in the graph. Select Reindex repository. If the repository has no commits on its default branch, GitLab sync reports repository_empty: “This repository has no commits on its default branch yet.” Push a commit first.

​
Plan limits stop a build

Messages such as Monthly indexing allowance used or Daily build limit reached mean a plan limit, not a fault. See Rate limits and plan limits. If a build stays stuck, use Get in touch under Settings in the console.

​
Query, Ask, and reindex errors

Per-workspace limits: Ask 30, query 120, and test impact 60 requests a minute. The hosted MCP allows 240 a minute per client IP. See Rate limits.

​
Repository connect issues

​
GitHub repositories are missing

On the Repositories page, select Add GitHub repositories. It opens GitHub, where you choose which repositories the Graphify app can access. A repository you didn’t grant there won’t appear. See GitHub.

​
GitLab: “GitLab is not connected.” or “Reconnect GitLab to continue.”

Graphify supports GitLab on gitlab.com only. Self-managed GitLab isn’t supported. Open Integrations, then select Connect on the GitLab card. If you see gitlab_reconnect_required, connect again. Other GitLab errors: See GitLab.

​
MCP client config mistakes

Per-client setup is in Integrations.

​
Graphify vs Graphify Local confusion

See Graphify vs Graphify Local.

​
Still stuck

FAQs

Common questions.

Hosted MCP

Setup and verification.