Skip to main content
Connect with your Nimt account using OAuth or a personal access token. Both methods use your existing permissions within one selected workspace. For ChatGPT and Claude, start with the client guide and use OAuth. Keep PATs for clients that need a bearer token; never paste one into a chat.

​
Workspace boundaries

A connection is tied to one workspace. It can discover projects there and use project-scoped tools only for projects belonging to that workspace. Knowing a project ID from a different workspace does not give the connection access to it. Switching workspaces in the Nimt app does not retarget an existing connection. To use another workspace, approve a separate OAuth connection or create a token while that workspace is active. If your client supports multiple server entries, give them distinct names so you can tell them apart. Nimt checks your current membership on requests. If you lose access to the workspace or your account is disabled, the credential no longer authorizes MCP access there.

​
Permissions

OAuth clients request scopes, which appear on the consent screen. They may also request the standard openid, profile, and email scopes for account identity and profile information. Review every permission before approving.
PATs created in Nimt include both mcp:read and mcp:write; the creation form does not offer a read-only option. OAuth may also request both. Review requested changes before allowing your assistant to call a write tool.
Workspace-member and billing tools also require organization owner or admin access. Nimt enforces these permissions on every request. Your client’s confirmation prompts give you an opportunity to review changes before they run.

​
Data shared with your assistant

The AI service receives the results of tools it calls. Depending on your request and permissions, this can include project settings, prompt text, analytics, citations, and brand information. For organization owners and admins, it can also include workspace members’ names and emails, subscription details, and credit usage. Review the AI service’s data retention and model-training settings, and follow your organization’s policies when connecting. Nimt authorization does not change the AI service’s data policies. Disconnecting stops future access through that approval. It does not erase information already returned to a conversation; manage that content with the AI service’s own controls. Do not include tokens or OAuth callback URLs in support requests or screenshots.

Connect with OAuth

Sign in, choose a workspace, and manage connected apps.

Use a personal access token

Create, store, and revoke a token.