From ZIP to connected in a few minutes.

Requirements

Component	Requirement
WordPress	6.5 or later
PHP	7.4 or later
Elementor (free)	Required for the page-building tools
WooCommerce	Optional — enables the commerce tools
Yoast SEO or Rank Math	Optional — enables the SEO write/inspect tools
Contact Form 7 / WPForms	Optional — enables deep form inspection

Tools whose integration is missing answer dependency_missing instead of failing obscurely, and the Diagnostics screen separates supported integrations from detected-but-unsupported ones.

1. Install and activate

1. Download liyans-mcp.zip from the Downloads page and verify its SHA-256 if you want certainty about the file.
2. In wp-admin, go to Plugins → Add New → Upload Plugin, choose the ZIP and click Install Now.
3. Click Activate Plugin. Activation creates the plugin’s two tables and its default options — nothing else on the site changes.
4. Open LIYANS MCP → Diagnostics and confirm the checks pass: PHP and WordPress versions, database version, the log and snapshots tables, and the MCP endpoint.

2. Create a connection token

1. Go to LIYANS MCP → Connection. The screen opens with a status strip (endpoint with a copy button, server state, active connections) and setup cards for Claude, ChatGPT and other MCP clients.
2. Give the token a label (for example, the name of the app or machine that will use it). The form starts from a recommended preset — label pre-filled, the read, write, media, seo, settings and devices scopes ticked, Publish and Commerce left unticked with the reasons printed next to the list — adjust it to what the connection actually needs.
3. Tick only the scopes that connection needs — the least that does the job. A read-only token is ideal for a first look.
4. Optionally set an expiry (30, 90 or 365 days, or never).
5. Click Create token and copy the secret immediately: it is shown once, and only its hash is stored.

3. Point your MCP client at the site

The Connection screen’s setup cards carry a copy-ready configuration block for each client, and the AI Clients screen goes further: a card per known client with its own setup guide, a copy-ready configuration block in that client’s own format, and the connections that client actually holds. Most clients accept a server definition like this (adjust to your client’s format):

{
  "mcpServers": {
    "liyans-mcp": {
      "url": "https://your-site.com/wp-json/liyans-mcp/v1/mcp",
      "headers": {
        "Authorization": "Bearer lym_your_token_here"
      }
    }
  }
}

Then try a safe first request: “Inspect this site and list its pages.” The call appears in LIYANS MCP → Logs, and the Connection screen shows the token’s last-used time.

4. Optional: enable OAuth 2.1

OAuth is off by default and is only needed for clients that use a sign-in flow instead of a pasted token.

1. Go to LIYANS MCP → Settings and open the Authentication section of the Settings Center.
2. Turn on Enable OAuth. Dynamic client registration is on by default; the registered-client limit bounds how many clients can wait for approval.
3. New clients register and stay pending; approve or revoke them on the OAuth screen. A registering client may ask to be confidential (client_secret_basic or client_secret_post) and then receives its secret exactly once — only its hash is stored. The consent screen always names the client and the requested scopes, and only a signed-in administrator can consent.
4. Discovery documents (RFC 8414 / RFC 9728) are served from the site automatically once OAuth is on.

Upgrading

1. Download the newer liyans-mcp.zip.
2. Plugins → Add New → Upload Plugin, choose the ZIP, Install Now.
3. WordPress detects the installed plugin and offers Replace current with uploaded — confirm it. Settings, tokens, sessions and logs are preserved.
4. Confirm the new version on the Plugins screen and re-check Diagnostics.

Uninstalling

Deactivate and delete the plugin from the Plugins screen as usual. The uninstaller removes everything the plugin itself wrote — its options, its log and snapshots tables, its cron event and its one-time-secret transients. It never touches posts, pages, media, products or any other content: drafts the assistant built remain in your WordPress, yours to keep or tidy like any other content.