Fastest way: one command
/audit skill for the Guided Audit Conductor. Skip to Verify it works below.
For details on the connect command, scope flags, and manual setup, see Connect with one command.
Manual MCP setup (if you prefer)
If you want to configure Claude Code manually:1. Get a Personal Access Token
Go to Settings → API Tokens in your Audity workspace and create a token with Read + Write scopes. It starts withaky_ and is shown only once.
2. Add the MCP server
Claude Code manages MCP servers through its ownclaude mcp CLI. Register Audity with:
--scope user adds it globally for every project; use --scope project to add it to a single repo’s .mcp.json instead.
3. Reload and test
Start a new Claude Code session (it loads MCP servers at startup), then ask:audity_list_projects and return your real projects. You now have 100+ audity_* tools as first-class operations with typed parameters and schema validation.
Optional: Direct API via CLAUDE.md (no MCP dependency)
If you need zero external dependencies or docs.auditynow.com isn’t reachable, Claude Code can call the Audity REST API directly using Bash.1. Set your token as an environment variable
2. Add the Audity context to your CLAUDE.md
Copy this into your global~/.claude/CLAUDE.md or your project’s CLAUDE.md:
Verify it works
Ask Claude Code:Using the /audit skill (Claude Code only)
If you installed the/audit skill via connect, use it for guided workflow:
/audit skill auto-orchestrates the pipeline (step order, cost preview, job polling, confidence flagging). See Guided Audit Conductor for details.
Example prompts (MCP or direct API)
Troubleshooting
Claude Code says Audity tools aren't available (MCP path)
Claude Code says Audity tools aren't available (MCP path)
Run
claude mcp list to confirm the server is registered. If it’s listed but tools don’t appear, start a new Claude Code session (MCP servers load at startup). Check that app.auditynow.com/api/mcp is reachable.Claude says it doesn't know the Audity API (CLAUDE.md path)
Claude says it doesn't know the Audity API (CLAUDE.md path)
Confirm the file is at
~/.claude/CLAUDE.md (global) or at your project root. Start a new Claude Code session after saving.401 on every request (direct API path)
401 on every request (direct API path)
Run
echo $AUDITY_TOKEN. If it’s empty, add the export to your shell profile and reload, or prefix the session with AUDITY_TOKEN=aky_... claude.401 PAT_MALFORMED
401 PAT_MALFORMED
Token format is wrong. Check that your header is exactly
Authorization: Bearer aky_<token> (no double Bearer).403 PAT_SCOPE_INSUFFICIENT
403 PAT_SCOPE_INSUFFICIENT
Token lacks
write scope. Generate a new token in Settings → API Tokens with Read + Write checked.What’s next
- Run a full audit workflow, the end-to-end recipe from intake to deliverables
- Working with Nucleus, memories, captures, insights, contacts
- Authentication, token scopes, rotation, error codes

