Use this guide to troubleshoot common issues with Notta MCP and Notta CLI. Find the issue that matches what you see, then try the checks below.
Note: For MCP, ask your AI assistant to call the named tool. For CLI, run the command in your computer's terminal or command-line app.
Notta is not found or MCP tools are missing
Check that the package for the tool you use is installed.
npm list -g @notta-labs/notta-mcp --depth=0
npm list -g @notta-labs/notta-cli --depth=0Run only the command for the tool you use. If the package is missing, follow the setup guide for that tool.
-
CLI: Reopen your terminal, then run
notta --version. -
MCP: Check the
nottaentry in your assistant's configuration, then fully quit and reopen the assistant.
If MCP still cannot find notta-mcp, check your assistant's setup guidance for locating installed commands. If you contact support, include the exact error message.
If a specific command or tool is unavailable, check that your installed version matches the guide. Older releases may use different command names.
Sign-in fails or credentials are missing
Start a fresh sign-in using the tool you installed.
| Action | MCP tool to request | CLI command |
|---|---|---|
| Start sign-in | auth_setup |
notta auth setup |
| Check authorization | auth_status |
notta auth status |
| Check the connected account | auth_user_info |
notta auth user info |
Complete the browser steps, then check authorization and the connected account. Opening the sign-in page does not confirm that sign-in succeeded.
For Invalid authorization request, a callback state mismatch, or a sign-in that keeps waiting:
- Cancel the unfinished attempt and close its authorization tab.
- Start one fresh sign-in and complete it using the new page.
- If the same error returns, contact support with the error message and package version.
Note: Do not delete credential files, change authorization URLs, or switch environments unless support directs you to do so.
A recording does not appear
Confirm that you connected the correct Notta account and that you have access to the recording in Notta. Try a shorter search keyword, or list recordings instead.
Results may span several pages. With MCP, ask your assistant to fetch the next page. With CLI, use the returned next_cursor value.
notta record list --cursor "NEXT_CURSOR"Replace NEXT_CURSOR with the value from the previous list response. For search results, continue with the same keyword and the search command's --cursor option.
MCP rejects an Upload or Download path
Confirm that the upload file or download destination is inside a folder listed in your MCP configuration's args.
- Use full paths to existing folders.
- Check that your computer account can read from or write to that folder.
- After changing the configuration, fully restart your assistant.
Tip: Avoid granting access to your entire home folder. Add only the folders you need.
A transcript is not ready
Check the existing recording's status before uploading the file again.
For MCP, request record_status with the record ID. For CLI, replace RECORD_ID below.
notta record status RECORD_IDIf the transcript is still processing, check again later. If it failed, keep the record ID and error message for support. A wait timeout alone does not confirm that transcription failed.
An export will not download
Check the export task before creating another one. For MCP, request export_status. For CLI, replace TASK_ID with the export task ID, not the record ID.
notta export status TASK_IDDownload only after the export succeeds. Check the destination folder and use a new filename if a file already exists. For MCP downloads, the destination must also be inside a configured folder.
Still need help?
If you have any questions about Notta MCP or CLI, please contact our support team at support@notta.ai.
When contacting support, include the following information:
- Your operating system
- The package version
- The assistant name, if you are using MCP
- The exact error message
- The record ID or export task ID, if relevant
Note: Remove passwords, tokens, authorization links, and private recording content before sharing screenshots or logs. Never send your credentials file.
FAQs
No. Complete the browser steps, then check authorization with auth_status or notta auth status.
No. Check the existing recording status first. If it is still processing, wait and check again later.
The file or destination may be outside the folders allowed in your MCP configuration. Use a full path inside a configured folder, then restart your assistant after changing the configuration.