Connect Claude Code
When you build a client’s site in Claude Code, it can read the work you’ve done in Axidus: the client’s Profile, their brand kit, the style guide’s exact colors and fonts, the site plan’s pages and sections, and the audit’s must-fix list. You ask for “CIVTAC’s home page”, and it starts from what you already know about CIVTAC instead of a pasted summary.
A Read key can read your business’s work, but it can’t change anything, start a job or spend anything. A Read and write key, which only the business’s owner can make, also lets Claude Code save what it writes as a client’s work and upload report exports. It never deletes anything or changes a client’s Profile.
1. Make a key
Section titled “1. Make a key”In the app, open Settings > Connections, give the key a name that says where it’s used (like “Claude Code on my laptop”), choose what it can do (Read, or Read and write) and select Create key.
The key is shown once. Copy it now, or copy the ready-made command under it. If you lose a key, revoke it and make a new one.
2. Add it to Claude Code
Section titled “2. Add it to Claude Code”Paste the command from Settings > Connections into a terminal and run it once:
claude mcp add --transport http axidus https://app.axidus.ai/mcp --header "Authorization: Bearer axk_..."Claude Code keeps the key from then on. Start a new Claude Code session
and run /mcp: axidus should show as connected.
3. Work on a client
Section titled “3. Work on a client”Ask for what you want in plain words, for example:
- “Build CIVTAC’s home page from their site plan.”
- “Use Harbor & Pine’s style guide as Tailwind tokens in this project.”
- “What does the audit say we have to fix on the product pages?”
Claude Code finds the client, then reads the Profile and the
work the task needs. To start with a checklist, run the
work_on_client prompt (/mcp__axidus__work_on_client) with the
client’s workspace. It asks Claude Code to:
- read the Profile and the relevant work first;
- use the style guide’s values exactly;
- treat the audit’s must-fix list as requirements;
- prefer approved work (drafts are fine to use);
- say what’s missing instead of making it up.
4. Write the monthly reports in Claude Code
Section titled “4. Write the monthly reports in Claude Code”With a Read and write key, the monthly search report and the monthly ads review can be written by your own Claude Code, at no cost on Axidus. Axidus still reads the exports, works out every number and checks the answer, and the report is saved in the client’s Work exactly as when Axidus writes it.
Run the monthly_search_report prompt
(/mcp__axidus__monthly_search_report) or the monthly_ads_review
prompt with the client’s workspace. Claude Code:
- uploads this month’s exports, if they aren’t in the workspace yet;
- asks Axidus to prepare the report, and reads its instructions and data;
- writes the report, then submits it; if a check fails, it fixes what Axidus names and submits again;
- gives you the link to the saved report.
The same works for a client’s site plan, its page copy and a
Google Search campaign plan: ask Claude Code to write one with
Axidus (the prepare_site_plan, prepare_page_copy and
prepare_campaign_plan tools). Axidus reads the client’s pages and their
style guide, audit or site plan, checks the answer the same way, and
saves it in the client’s Work.
5. Build a client’s site
Section titled “5. Build a client’s site”When a project has its site plan, style guide and page copy, make its build brief: on the project’s page, select Make the build brief. It joins everything a build needs (each page’s sections with their layout and copy, the style guide’s exact values, the audit’s must-fix list, the logo and the project’s build settings) and lists what’s missing first. It’s free, and made in a moment.
Then, in a fresh Claude Code session in the site’s repository, run the
build_client_website prompt (/mcp__axidus__build_client_website)
with the client’s workspace and the project, and optionally one page.
It asks Claude Code to:
- read the build brief first, and tell you its blockers and warnings before writing any code;
- build for the project’s platform (Shopify theme sections, a WordPress block theme, or the stack your repository uses);
- match the design tokens exactly and use the copy word for word, keeping every “[client to confirm: …]” visible;
- build every page and section in order, make what the client edits editable in the CMS you chose, and meet each must-fix item;
- download the logo and font files instead of redrawing them;
- finish with a checklist of what it built, what’s missing, and the staging address to re-audit in Axidus.
A brief that isn’t ready can still be built from: Claude Code reports what’s missing and keeps it visible. When a project has no saved brief, or its sources changed since, Claude Code gets one assembled on the spot from the current work (it isn’t saved).
What it can read
Section titled “What it can read”- Your clients: each workspace, and how complete its Profile is.
- The Profile: every approved fact with its source and date, and the questions the client hasn’t answered yet.
- The brand kit: colors, fonts, the logo and brand files (as download links that work for 10 minutes), style notes and voice.
- Projects: the brief, the platform, the sites the client likes, and the project’s work and conversations.
- Projects: also their build settings (how the client edits the site, and the forms, integrations and analytics it needs) and whether the build brief is ready.
- Work: audits, style guides, site plans, page copy and
documents at their latest version, with their status. A style guide can
come as CSS variables, a Tailwind theme, a WordPress
theme.json, Shopify theme settings or design tokens; a site plan or page copy as Markdown or JSON, or one page at a time. - The build brief: a project’s brief as Markdown or JSON, what’s missing first, the whole site or one page at a time.
- Workspace memory: the summaries of your conversations with the specialists.
- Search: a word or phrase across the Profile, the work and the summaries.
Keep your keys safe
Section titled “Keep your keys safe”- A key reads everything in your business, so treat it like a password: don’t paste it into a shared chat or commit it to a repository.
- Anyone in your business can make and revoke keys. Revoking works immediately.
- Settings > Connections shows when each key was last used. A revoked key stays in the list, marked with the date, so you can check whether it was used afterwards.
- A business can have up to 10 active keys.
Other coding agents that can connect to a remote MCP server with a
header work the same way: use https://app.axidus.ai/mcp as the address
and send the key as Authorization: Bearer <key>.