Your WordPress administrator password is designed for you, not for an AI tool. A safer connection uses separate credentials, narrow permissions, and a clear record of every action. That gives the AI enough access to help without turning one leaked secret into control of the whole site.
Your admin password is the wrong credential
An administrator login can change users, plugins, themes, settings, content, and often store data. Sharing it with another service creates more access than most tasks need and makes it difficult to remove only that service later.
Use a credential created for the connection instead. It should belong to a named WordPress user, carry the smallest useful role, and be easy to revoke without changing the password you use every day.
Useful automation starts with a smaller key, not a copy of the master key.
Use a WordPress application password
WordPress application passwords are made for tools that use the REST API. They are separate from your normal login and can be removed individually. Claistore accepts the application password on the server, encrypts it, and does not return it to the browser or the AI provider.
- Create a dedicated WordPress user for the connection when practical.
- Give that user the lowest role that can complete the intended work.
- Name the application password clearly so you know what it belongs to.
- Revoke it immediately when the connection is replaced or no longer needed.
Treat WooCommerce as a separate connection
WordPress content and WooCommerce store operations use related but different APIs. Connect WooCommerce with its own consumer key and secret, then choose read-only or read/write access based on the real job.
A reporting agent that summarizes sales does not need permission to edit products or refund orders. Keeping the commerce connection separate makes that boundary easier to understand and change.
Put permissions between the store and the model
The AI should never receive the raw WordPress or WooCommerce credential. It should receive named tools such as listing posts, drafting a product description, or reading an order. Claistore uses MCP to present only the tools you have allowed.
- Start with read tools and confirm the returned data is correct.
- Add write tools one job at a time.
- Keep refunds, deletions, user changes, and store settings behind human approval.
- Review the activity log for the person, agent, tool, result, and cost of each run.
Test before you allow changes
Begin with a harmless request: list five recent posts or read a single product. Check that the right workspace, store, user, and agent appear in the activity record. Then try a draft-only action before allowing anything to publish or change live commerce data.
This gradual path is not red tape. It is how a store owner learns what the connection can do, catches a bad setting early, and builds confidence from evidence instead of promises.