audit_a_token — Nota MCP Prompt

audit_a_token is one of 2 prompts on the Nota MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke audit_a_token from your client

• Claude Code Nota Prompt/audit_a_token run in your project directory
• Claude Desktop Nota Prompt/audit_a_token ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Nota Prompt/audit_a_token ~/.cursor/mcp.json
• VS Code Nota Prompt/audit_a_token .vscode/mcp.json
• Zed Nota Prompt/audit_a_token ~/.config/zed/settings.json
• Windsurf Nota Prompt/audit_a_token ~/.codeium/windsurf/mcp_config.json
• Cline Nota Prompt/audit_a_token ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Nota Prompt/audit_a_token ~/.gemini/settings.json
• Grok Nota Prompt/audit_a_token .mcp.json (in your project root)
• ChatGPT Nota Prompt/audit_a_token Settings → Connectors → Advanced → Developer mode
• Claude.ai Nota Prompt/audit_a_token Settings → Connectors → Add custom connector
• LangChain Nota Prompt/audit_a_token pip install langchain-mcp-adapters

Other prompts on this server

• read_a_receipt

Nota also offers 26 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.