Skip to main content

Fastest way: one command

This auto-configures the Audity MCP server in Claude Code and optionally installs a /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 with aky_ and is shown only once.

2. Add the MCP server

Claude Code manages MCP servers through its own claude 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:
Claude Code will call 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

For a one-off session:

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:
If Claude returns real data, you’re connected. If it says “I don’t have access to Audity” or returns 401/403, jump to Troubleshooting.

Using the /audit skill (Claude Code only)

If you installed the /audit skill via connect, use it for guided workflow:
The /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

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.
Confirm the file is at ~/.claude/CLAUDE.md (global) or at your project root. Start a new Claude Code session after saving.
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.
Token format is wrong. Check that your header is exactly Authorization: Bearer aky_<token> (no double Bearer).
Token lacks write scope. Generate a new token in Settings → API Tokens with Read + Write checked.

What’s next