> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nimt.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Resolve connection, authentication, and workspace access issues.

Start by checking that Nimt has confirmed pre-release access for you. The public
service is not launched, so an unavailable endpoint or missing settings entry
does not necessarily mean your client is configured incorrectly.

## Cannot reach the server

* Check that the server URL is exactly `https://api.nimt.ai/mcp` and 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.

Opening the URL in a browser is not a connection test: MCP expects protocol
requests with authentication, not a normal web page. If the service remains
unavailable, contact Nimt with the time and error message.

## 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](/mcp/authentication/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.

For either authentication method, your account must still have access to the
connected workspace. The current MCP requires `mcp:read`; a write scope alone is
not sufficient. For OAuth, restart authorization if the required permission was
not granted. See [permissions](/mcp/authentication/overview#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.

## Project metadata is unavailable

Ask the assistant to discover the project again with `workspace_list_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.

Missing data coverage or a zero prompt count can reflect the project's current
state. Metadata does not include the underlying prompt results or reports.

## Connected, but a tool is missing

Refresh the client's tool list or reconnect, and make sure the Nimt server and
its tools are enabled. The initial catalog contains only `workspace_list_projects`
and `project_get_metadata`. Prompts asking for reports or edits do not make those
capabilities available.

## Get help

Email [support@nimt.ai](mailto:support@nimt.ai) with the client name and version,
authentication method, approximate time and timezone, and the error text. Include
the affected workspace name if relevant.

Never send PATs, authorization headers, OAuth codes, or complete callback URLs.
Redact credentials from logs and screenshots before sharing them.