Skip to main content
A personal access token (PAT) is a secret credential tied to your Nimt user and one workspace. Use it when your client supports bearer tokens but cannot complete OAuth, or when you need a non-interactive connection. For ChatGPT and Claude, use OAuth sign-in.

​
Create a token

1

Choose the workspace

Sign in to Nimt and switch to the workspace you want to connect. The token stays tied to this workspace even if you switch workspaces later.
2

Open Personal access tokens

Go to Settings → Personal access tokens, or open Personal access tokens. Give the token a recognizable name, such as Reporting client, and choose Expires after. Choose 30, 90, 180, or 365 days; the default is 90 days.
3

Create and save

Choose Create token, then Copy token. The complete token is shown only once and begins with nimt_pat_. Store it in a password manager or your client’s secure credential store. If you lose it, create a replacement.
New tokens allow both reading data and making changes (mcp:read and mcp:write). The creation form does not offer a read-only token. Read the permission rules before granting a client access.

​
Supply the credential

Configure the client’s remote MCP connection to send this header to https://api.nimt.ai/mcp:
Replace the placeholder, including angle brackets, with your token in a secure credential field. Do not put a token in a URL, repository, chat message, or screenshot. Organization API keys are not personal access tokens for MCP.

​
Use a token with Codex

The Codex token setup is in Other clients, alongside the OAuth configuration. Keep the token in the client’s secure environment rather than putting its value in a command or file that may be shared.

​
Revoke or replace a token

In the token’s workspace, return to Settings → Personal access tokens. Choose Revoke next to an active token and confirm. Clients using it lose access. Revoking a PAT does not disconnect a separate OAuth approval. For routine rotation, create a replacement, update the client, verify that it can list projects, and revoke the old token. If a token may have leaked, revoke it immediately before creating a replacement. Expired tokens must also be replaced.