Search for
anything.

Your site needs HTTPS and pretty permalinks on. Add your site as a custom connector using the MCP endpoint from ClaiStore → Settings (it looks like https://your-store.com/wp-json/claistore/v1/mcp), choose OAuth, and sign in as a WordPress administrator when prompted. Connector support depends on your AI provider and plan — not every client supports custom MCP connectors yet.

ClaiStore auto-approves known providers (claude.ai, openai.com, etc.); any other client has to pass a consent screen, and its redirect URI must be an absolute https:// URL (or http://localhost for local testing). A non-https redirect is rejected outright — that’s a deliberate security guard, not a bug.

Every ClaiStore site now needs to be linked to a free claistore.com account — this is separate from your WordPress login. Click Connect in ClaiStore → Settings, confirm on claistore.com/my-account, and you’re redirected straight back. There’s a grace period before anything is blocked, so nothing already running breaks the moment this shows up.

The one-click link is single-use and expires about 10 minutes after it’s generated. Go back to ClaiStore → Settings and click Connect again for a fresh link — no code to copy, just click through.

Most modern clients (Claude, ChatGPT) connect with one-click OAuth automatically. A few older or self-built MCP clients need the static bearer token instead — it’s shown in ClaiStore → Settings. The static token is read-only for paid marketing-channel writes; those always need an OAuth connection signed in as an administrator.

Content mode exposes only posts, pages, media and SEO tools. Store mode adds WooCommerce (products, orders, coupons) on its own. Both turns everything on. Pick whichever matches what you actually want the assistant to touch.

Reconnect the MCP client with OAuth, signed in as a WordPress administrator — the static bot token intentionally cannot do everything an admin-authenticated connection can (channel writes, theme editing, plugin management). On multisite, some actions need a super administrator specifically.

Yes — ClaiStore → Settings → Disable individual tools lets you switch off any single tool by name across every group, on top of the broader per-feature toggles.

Yes, every write is recorded with a before/after entry, including which channel and connector account made it — it’s in the ClaiStore dashboard’s activity log.

New posts default to draft status unless the assistant is explicitly told to publish or schedule one — check what status was actually requested. If posts keep going live unexpectedly, review the conversation that created them; ClaiStore doesn’t publish anything on its own initiative.

update_seo_meta writes to Yoast or Rank Math’s own fields — one of those plugins needs to be active. Use get_seo_head afterward to confirm the write actually reached the rendered page (past any cache).

From the tone you picked in the setup wizard, plus (if you’ve turned it on) the Knowledge store, which studies your published pages, catalogue and named competitors to keep a running profile of how your business talks about itself.

Upload with upload_media, then call set_featured_image with the returned attachment id — or pass featured_image_url directly on create_post to do both in one step.

WooCommerce needs to be installed, active, and Mode needs to be Store or Both. If it’s not installed yet, ClaiStore → Channels offers a one-click Install WooCommerce card.

That’s intentional PII protection — turn on "Return full customer contact details" in Settings if the assistant genuinely needs unmasked contact info and lifetime spend.

Each write path has its own flag: catalog/settings writes need "Allow WooCommerce writes", order-status changes need "Allow order status changes", and refunds need "Allow refunds" — all off by default, all in Settings → WooCommerce.

Double-check the date range — wc_analytics_* tools default to the last 30 days unless you pass after/before explicitly — and confirm you’re reading the right store currency, which is always returned alongside the numbers.

Turn on "Allow plugin install / update / remove" in Settings → Site care & knowledge. Only the wordpress.org directory is ever a source, and ClaiStore + WooCommerce can’t be removed this way.

"Let ClaiStore learn" is off by default. Turn it on in Settings → Site care & knowledge and a daily job studies your pages, catalogue, and any competitors you’ve named; knowledge_learn can also be run on demand.

Reads only need "Site care" tools on; writes additionally need "Database access" turned on, and even then a fixed denylist (site URL, active plugins, user roles, cron, ClaiStore’s own secrets) is always refused, and staging/dry-run blocks every write regardless.

Confirm "Cache purge" is on (it is by default) — ClaiStore auto-purges the specific page after a content, theme-file or database write, with built-in support for the common caching plugins and an optional Cloudflare zone purge.

Connect it under ClaiStore → Channels — each channel routes through the Connector Broker so your site never stores the provider’s app secret directly, only a short-lived, scoped token.

Writes need an OAuth admin connector (never the static token) plus the matching write flag on in Settings → Marketing channels; actually launching or raising a budget additionally needs the launch flag, confirm_spend:true, and to stay under your daily budget cap.

That’s expected — each platform counts and attributes differently. marketing_overview and attribution_compare show all three side by side and flag the gap rather than silently averaging or summing mismatched currencies.

That means it’s connected in read-only mode. Disconnect and reconnect it in ClaiStore → Channels, and approve the write / indexing permission this time.

Bundled writing playbooks (SEO article, blog post, product description, category page, and more) that ship with ClaiStore, get tokenized to your site during setup, and are exposed to your AI client as ready-to-use prompts.

Yes, with "Skill editing" on in Settings plus an administrator connector — upsert_skill changes the body, title, or description, and reset_skill restores the original bundled version if you want to start over.

Re-run the setup wizard’s content step to change the stored tone, or edit the specific skill directly — skill edits are flagged custom so a plugin update never silently overwrites your changes.

No — by design. Editing an existing theme file requires a targeted find-and-replace of an exact, unique snippet; a full-file rewrite is only possible with an explicit whole_file_rewrite flag the assistant has to deliberately set. A request like "just change this label" mechanically cannot turn into a layout change.

theme_file_history lists every version of a file with what changed and when; theme_revert_file can restore any of them, or restore straight to "origin" — the very first version ever saved, which is never deleted no matter how many edits come after it.

That’s intentional — file editing only ever works over an OAuth connection signed in as a WordPress administrator, never the static MCP token, and only once "Theme file editor" is turned on in Settings → Site care & knowledge.

Only with "Edit any installed theme" or "Allow mu-plugin editing" turned on specifically — both off by default, both under Settings → Site care & knowledge.

They block every write — content, WooCommerce, database, theme files, everything — so you can rehearse a connection or a migration without any risk of a real change landing.

That’s the denylist from setup — domains you’ve marked as do-not-adopt are never fetched and never used as a source of voice or claims, only as competitive awareness.

It auto-suppresses itself while Yoast or Rank Math is active, since they already emit their own. If neither is running, turn on "Article structured data" in Settings → Guardrails.

No, but it’s supported if you have one — WP Rocket, W3 Total Cache, WP Super Cache, WP Fastest Cache, Cache Enabler, SG Optimizer, LiteSpeed and a few others are auto-detected and purged after a relevant write.

Yes, optionally — set your Cloudflare zone id and an API token (scoped just to cache purging) in Settings, and content/theme/database writes will purge that zone as well as any local cache plugin.

Sign in at claistore.com/my-account, pick the connected site, and choose a tier — checkout runs through Stripe. See claistore.com/pricing for exactly what each tier unlocks.

My account → Manage billing opens the Stripe billing portal, where you can update payment details, change plan, or cancel — cancelling stops future billing, it doesn’t retroactively charge or refund the current period on its own.

Each tool has a minimum tier — the error names the exact tier it needs and your account’s current one. Upgrade the specific site from claistore.com/my-account; every tier includes everything in the ones below it.

Pricing, billing cycle and cancellation terms are shown before you subscribe to any paid tier, and refund requests are handled case by case — email support@claistore.com and we’ll sort it out. See the Terms of Service for the full billing terms.

Linked in the footer of every page, and under Resources in the header — or go straight to claistore.com/terms and claistore.com/privacy.