# WordPress MCP Access

Keep this access method disabled.
No MCP client or server is selected.
Do not use MCP through this scaffold.

## Required variables

- `SITE_URL`: The HTTPS URL of the WordPress site.
- `WP_REST_USER`: The name of the approved WordPress account.
- `WP_REST_APPLICATION_PASSWORD`: The application password from an approved private source.

`server.example.json` lists environment variable names as data.
The JSON file does not expand environment variables.
Do not store credentials in the repository.

## Least-privilege account requirements

Use a dedicated WordPress account.
Give the account only the permissions that the approved read operations require.
Do not give the account permission to create, update, publish, or delete content.
Revoke the application password when access is no longer necessary.

## Manifest controls

Keep `enabled` set to `false` in the repository manifest.
The `.example` suffix and `enabled: false` value are documentation controls.
These controls do not prove that an unknown client disables the configuration.
Do not load the manifest directly into an MCP client.
After approval, translate the manifest into the selected client's schema.
Configure only the approved server.
Use the `stdio` transport.
Load the approved credentials from the local environment.

## Verification limitation

This scaffold does not include an MCP verification command.
MCP stays disabled.
WordPress updates the application-password `last_used` and `last_ip` metadata after authenticated use.
This metadata update is a production write.
This scaffold cannot validate production application passwords without a WordPress metadata write.
Keep the credential placeholders for future separately approved access.
Do not use the credential placeholders through this scaffold.

## Prohibited actions

Do not use MCP tools that create, update, publish, upload, or delete data.
Do not install or update WordPress components.
Do not change users, roles, settings, themes, or plugins.
Do not bypass TLS verification.

## Production write boundary

This repository never authorizes production writes.
Operator approval does not enable writes through this template.
Use a separate access method for an approved production write.
Use a change procedure outside this scaffold for that write.

## Required approval

Use a separate access procedure before you translate the manifest or enable MCP access.
Get operator approval for that specific access.
The approval must identify the MCP client, server, account, and credentials.