Djangify has two related but separate AI features: a set of bring-your-own-key AI tools inside the admin, and an MCP connector that lets you (or Claude, on your behalf) manage the shop directly from a chat instead of clicking through the admin. Both are optional, both are off until you connect a key, and you don't have to use all of them — you can pick just the ones that are actually useful to you.
\r\nThe AI Tools (In-Admin)
\r\nOnce you connect your own provider key (Anthropic, OpenAI or Google) under AI Settings, each of these can be switched on individually:
\r\n- \r\n
- Site Audit — a free, rule-based scan of your catalogue, pages, blog and SEO/EEAT setup that runs for everyone with no key needed at all. Connecting a key adds a deeper AI-powered layer on top. If you only want one thing from this list, this is the one to keep — it costs nothing to run as often as you like. \r\n
- Product description writer — drafts or improves a description from a title and a few details. \r\n
- Blog post writer — drafts or expands a full post from a topic; lands as a draft, never publishes itself. \r\n
- Blog AI-summary writer — drafts the short AI/GEO summary box shown at the top of a post. \r\n
- FAQ generator — drafts question/answer pairs for an FAQ block from a topic. \r\n
- Djangify Assistant — an in-admin chat (with history) for talking through how to run and grow your shop, optionally using your own live site data as context. \r\n
- Store Setup wizard — fill in one form (branding, homepage, shop display, pages, tools) and apply it in one go instead of clicking through every settings page yourself. \r\n
You choose which of these to turn on. If you only care about SEO housekeeping, enable Site Audit and skip the writers. If you'd rather draft content yourself, skip the writers and keep the Assistant for questions instead. Every AI call is logged, and you can set an optional monthly cap as a safety net regardless of which features you use.
\r\nThe MCP Connector (Managing From Claude Directly)
\r\nThe MCP connector is a different thing: instead of clicking through the admin, it lets you open Claude wherever you already are and ask it to create or edit products, posts and pages, tune SEO, or run a site audit — in conversation. It uses the same tools behind the scenes as the in-admin AI features above, just driven from Claude instead of the admin UI.
\r\nOn managed hosting: this is the simpler path. Connect your Claude account from the admin's Connect to Claude page — there's nothing to install, the hosting handles the connector for you.
\r\nOn self-hosted: the connector runs as a lightweight sidecar process alongside your main application — a second systemd service — and needs two extra reverse-proxy routes (/mcp* and /.well-known/oauth-protected-resource*) pointed at it. Setup is three pieces: register the OAuth client (python manage.py mcp_create_client), run the sidecar as its own systemd service, and add those two Caddy or Nginx routes. Once that's done, add the connector in Claude using just your site's /mcp URL — Claude's own UI handles the OAuth flow, so there's no client ID or secret to paste in by hand. The in-admin Connect to Claude page shows the URL and whether it's currently connected.
\r\nThe connector is off by default in both cases, and every action it takes is logged under MCP Call Log so you can see exactly what changed and when.
\r\n\r\n