https://api.nimt.ai/mcp over Streamable HTTP. OAuth is the
recommended authentication method. Client setup support is not a guarantee that
every client version has been tested; update your client and check its own docs.
Cursor
Add the following entry to~/.cursor/mcp.json. Merge it into the existing
mcpServers object if you already have other servers.
Claude Code
Add Nimt to your personal Claude Code configuration:/mcp inside Claude Code, select Nimt, and authenticate. Complete the Nimt
sign-in and workspace approval in your browser. See
Claude Code’s MCP documentation.
Codex
Add the server and sign in from the Codex CLI:/mcp in the Codex terminal
UI to inspect the connection. See
Codex’s MCP documentation.
Use a token with Codex
If OAuth is unavailable, create a PAT and makeNIMT_PAT available to the process launching Codex through your secret
manager or a secure shell prompt. Then add a separate token-based entry:
Other remote MCP clients
Add a custom server with the Nimt URL and Streamable HTTP transport. Start the client’s OAuth flow and approve a workspace in Nimt. If it cannot complete OAuth but accepts custom HTTP headers, follow the personal access token guide. Clients that only support local stdio servers cannot connect to this URL directly. Nimt does not require a proxy for clients with native remote MCP support. Do not confuse an AI provider’s API key or a Nimt organization API key with a Nimt personal access token. Never store credentials in shared configuration files.Verify your connection
Use Nimt to list the projects in my connected workspace.Then ask for the metadata of one returned project. See available tools, usage limits, and troubleshooting for the current contract.