Cannot add Nimt in ChatGPT or Claude
Check your client account, plan, and administrator policy. ChatGPT’s manual connection requires developer mode on the web. Claude organization members may need their owner to add the connector first. Use the current ChatGPT guide or Claude guide.Cannot reach the server
- Check that the server URL is exactly
https://api.nimt.ai/mcpand the client supports Streamable HTTP. - Check your network and any proxy or firewall restrictions on HTTPS requests.
- Update the client and retry its connection flow.
Tools report that there is no active plan
Tools and prompts work only while the connected workspace has an active plan. Your assistant can still connect and list tools. Choose a plan on the Plans page, and your existing connection works again without reconnecting.Cannot find credential settings in Nimt
Open Connected apps to manage OAuth approvals or Personal access tokens to manage tokens in your current workspace. Sign in as yourself; credential management is not available while impersonating another user. If you still cannot open these pages, contact support@nimt.ai.OAuth sign-in fails or keeps repeating
Confirm you signed in with the right Nimt account and selected a workspace you still belong to. Review the client’s connection status and restart its authentication flow. Do not reuse a bookmarked consent page or callback URL. If the client reports an invalid resource or audience, check the configured server URL. It must use the public MCP URL as the OAuth resource. A current MCP client should discover the authorization settings automatically. If renewal fails, sign in again. Access tokens are short-lived, and renewal requires an active approval, workspace membership, and valid refresh credentials. See OAuth.Unauthorized or missing permissions
For a PAT, confirm that:- You are using a personal access token beginning with
nimt_pat_. - The token has not expired or been revoked.
- The client sends
Authorization: Bearer <token>with no extra whitespace in the token value. - Any configured token environment variable is available to the client process.
mcp:read to connect and mcp:write for
changes; a write scope alone is not sufficient. Workspace-member and billing
tools also require organization owner or admin access. For OAuth, restart
authorization if a required permission was not granted. See
permissions.
No projects, or the wrong projects
A connection sees only its approved workspace. Switching the workspace in the Nimt app does not change an existing OAuth approval or PAT. Check that workspace in Nimt. Clear any project search, and ask the assistant to fetch additional pages if the list is incomplete. If you connected the wrong workspace, create a new approval or token for the intended workspace.A project is unavailable
Ask the assistant to discover the project again withlist_projects,
then use the returned ID. A project from another workspace, or a project that is
no longer available, cannot be accessed through this connection.
A missing brand, unavailable reporting dates, or a zero prompt count can reflect
the project’s current state. For performance data, ask the assistant to use the
analytics tools.
Connected, but a tool or guided workflow is missing
Refresh the client’s tool and prompt lists or reconnect, and make sure the Nimt server is enabled. Compare tools with the current tool catalog. Clients can cache server capabilities, so reconnect after Nimt announces a catalog change. MCP prompts are optional client functionality. If your client does not show the guided workflows, copy the example request from the workflow page into the conversation instead.The assistant answers without calling Nimt
A connected account is not necessarily enabled in every conversation. Select Nimt in the client’s conversation controls and explicitly ask it to use Nimt. Check its tool activity to see whether it retrieved your project data. If the request changes data, make the intended final state explicit and review the proposed changes before confirming them.Rate limits or timeouts
For HTTP429, wait for the Retry-After period before trying again. Other
connections for your user and workspace share the same quota. Reduce parallel
requests and avoid rapid reconnection attempts.
If a request for data times out, try a smaller request. If a request to change
data times out, check the project or creation status before repeating it; the
change may have completed. Record the time if the problem persists.
See usage limits for the current allowances and retry advice.
Results differ from another answer or the dashboard
Check that you are comparing the same workspace, project, reporting period, model, and filters, and that you fetched every page.- Reporting periods: The dates analyzed may be narrower than the dates you requested if the project has limited data. Ask the assistant to state the analyzed period and the comparison period used for trends.
- Missing values: An unavailable value is not zero. A missing comparison period means there is no previous value to compare against.
- Brand leaderboards: Your own brand may appear as an extra row outside the requested page. Include it once when combining pages.
- Prompt counts: Metadata counts active, non-deleted prompts. Tag counts overlap when a prompt has several tags, so adding them can exceed the total prompt count. Tags with no active prompts can still appear, and prompts can be unclassified.
- Models: A currently tracked model may not have produced stored data yet. A previously observed model may no longer be tracked.
- Dates: The reporting range does not guarantee data for every day or every model between its endpoints. The time metadata was fetched is not the time a prompt last ran.