@automattic/mcp-wordpress-remote 0.2.9 → 0.2.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -49
- package/dist/proxy.js +4472 -349
- package/package.json +8 -3
package/README.md
CHANGED
|
@@ -62,7 +62,7 @@ You need to install the [wordpress-mcp](https://github.com/Automattic/wordpress-
|
|
|
62
62
|
|
|
63
63
|
### 1. OAuth 2.1 (Recommended - MCP Compliant)
|
|
64
64
|
|
|
65
|
-
OAuth 2.1 provides the most secure and user-friendly experience with full MCP Authorization specification compliance
|
|
65
|
+
OAuth 2.1 provides the most secure and user-friendly experience with full MCP Authorization specification compliance.
|
|
66
66
|
|
|
67
67
|
#### **For Self-Hosted WordPress Sites:**
|
|
68
68
|
|
|
@@ -74,32 +74,14 @@ OAuth 2.1 provides the most secure and user-friendly experience with full MCP Au
|
|
|
74
74
|
"args": ["-y", "@automattic/mcp-wordpress-remote"],
|
|
75
75
|
"env": {
|
|
76
76
|
"WP_API_URL": "https://your-wordpress-site.com",
|
|
77
|
-
"OAUTH_ENABLED": "true"
|
|
78
|
-
"OAUTH_FLOW_TYPE": "authorization_code",
|
|
79
|
-
"OAUTH_USE_PKCE": "true"
|
|
77
|
+
"OAUTH_ENABLED": "true"
|
|
80
78
|
}
|
|
81
79
|
}
|
|
82
80
|
}
|
|
83
81
|
}
|
|
84
82
|
```
|
|
85
83
|
|
|
86
|
-
#### **For WordPress.com Sites (Automatic Compatibility):**
|
|
87
84
|
|
|
88
|
-
```json
|
|
89
|
-
{
|
|
90
|
-
"mcpServers": {
|
|
91
|
-
"wordpress": {
|
|
92
|
-
"command": "npx",
|
|
93
|
-
"args": ["-y", "@automattic/mcp-wordpress-remote"],
|
|
94
|
-
"env": {
|
|
95
|
-
"WP_API_URL": "https://yoursite.wordpress.com"
|
|
96
|
-
}
|
|
97
|
-
}
|
|
98
|
-
}
|
|
99
|
-
}
|
|
100
|
-
```
|
|
101
|
-
|
|
102
|
-
_The system automatically detects WordPress.com sites and uses compatible OAuth2 endpoints._
|
|
103
85
|
|
|
104
86
|
**MCP Authorization Specification Features:**
|
|
105
87
|
|
|
@@ -178,7 +160,7 @@ To create an application password:
|
|
|
178
160
|
"args": ["-y", "@automattic/mcp-wordpress-remote"],
|
|
179
161
|
"env": {
|
|
180
162
|
"WP_API_URL": "https://your-wordpress-site.com",
|
|
181
|
-
"OAUTH_CALLBACK_PORT": "
|
|
163
|
+
"OAUTH_CALLBACK_PORT": "7665",
|
|
182
164
|
"OAUTH_HOST": "127.0.0.1",
|
|
183
165
|
"WP_OAUTH_CLIENT_ID": "your-custom-client-id"
|
|
184
166
|
}
|
|
@@ -213,11 +195,15 @@ For WooCommerce-specific tools and reports:
|
|
|
213
195
|
| ---------------------------- | ---------------------------------- | -------------------- | -------- |
|
|
214
196
|
| `WP_API_URL` | WordPress site URL | - | ✅ |
|
|
215
197
|
| `OAUTH_ENABLED` | Enable OAuth authentication | `true` | - |
|
|
216
|
-
| `OAUTH_CALLBACK_PORT` | OAuth callback port | `
|
|
198
|
+
| `OAUTH_CALLBACK_PORT` | OAuth callback port | `7665` | - |
|
|
217
199
|
| `OAUTH_HOST` | OAuth callback hostname | `127.0.0.1` | - |
|
|
218
200
|
| `WP_OAUTH_CLIENT_ID` | Custom OAuth client ID | - | - |
|
|
201
|
+
| **OAuth Endpoints** | | | |
|
|
202
|
+
| `OAUTH_AUTHORIZE_ENDPOINT` | OAuth authorization endpoint | - | ✅ (for custom OAuth) |
|
|
203
|
+
| `OAUTH_TOKEN_ENDPOINT` | OAuth token endpoint | - | ✅ (for custom OAuth) |
|
|
204
|
+
| `OAUTH_AUTHENTICATE_ENDPOINT`| OAuth authenticate endpoint | - | - |
|
|
219
205
|
| **MCP OAuth 2.1 Settings** | | | |
|
|
220
|
-
| `OAUTH_FLOW_TYPE` | OAuth flow type
|
|
206
|
+
| `OAUTH_FLOW_TYPE` | OAuth flow type (authorization_code or implicit) | `authorization_code` | - |
|
|
221
207
|
| `OAUTH_USE_PKCE` | Use PKCE (required for OAuth 2.1) | `true` | - |
|
|
222
208
|
| `OAUTH_DYNAMIC_REGISTRATION` | Enable dynamic client registration | `true` | - |
|
|
223
209
|
| `OAUTH_RESOURCE_INDICATOR` | Use resource indicators (RFC 8707) | `true` | - |
|
|
@@ -232,33 +218,7 @@ For WooCommerce-specific tools and reports:
|
|
|
232
218
|
| `WOO_CUSTOMER_KEY` | WooCommerce consumer key | - | - |
|
|
233
219
|
| `WOO_CUSTOMER_SECRET` | WooCommerce consumer secret | - | - |
|
|
234
220
|
|
|
235
|
-
### WordPress.com Compatibility
|
|
236
221
|
|
|
237
|
-
The package automatically detects WordPress.com sites and uses the appropriate OAuth2 flow for full compatibility with the [WordPress.com OAuth2 API](https://developer.wordpress.com/docs/oauth2/).
|
|
238
|
-
|
|
239
|
-
#### **Automatic Detection**
|
|
240
|
-
|
|
241
|
-
WordPress.com sites (\*.wordpress.com) are automatically detected and configured with:
|
|
242
|
-
|
|
243
|
-
- **Standard OAuth2 implicit flow** (as per WordPress.com documentation)
|
|
244
|
-
- **WordPress.com OAuth endpoints**: `public-api.wordpress.com/oauth2/*`
|
|
245
|
-
- **Bearer token authentication** format
|
|
246
|
-
- **No PKCE requirement** (WordPress.com compatible)
|
|
247
|
-
|
|
248
|
-
#### **Manual WordPress.com Configuration**
|
|
249
|
-
|
|
250
|
-
For explicit WordPress.com mode:
|
|
251
|
-
|
|
252
|
-
```json
|
|
253
|
-
{
|
|
254
|
-
"env": {
|
|
255
|
-
"WP_API_URL": "https://yoursite.wordpress.com",
|
|
256
|
-
"OAUTH_FLOW_TYPE": "implicit",
|
|
257
|
-
"OAUTH_USE_PKCE": "false",
|
|
258
|
-
"OAUTH_RESOURCE_INDICATOR": "false"
|
|
259
|
-
}
|
|
260
|
-
}
|
|
261
|
-
```
|
|
262
222
|
|
|
263
223
|
### Disable OAuth
|
|
264
224
|
|