@websamurai/mcp-wp-remote 1.0.2 → 1.0.3
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 +11 -11
- package/index.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
# @
|
|
1
|
+
# @websamurai/mcp-wp-remote
|
|
2
2
|
|
|
3
|
-
A STDIO bridge for connecting to WordPress sites via the Model Context Protocol (MCP). This package enables communication between MCP clients and WordPress installations running the
|
|
3
|
+
A STDIO bridge for connecting to WordPress sites via the Model Context Protocol (MCP). This package enables communication between MCP clients and WordPress installations running the websamurai plugin.
|
|
4
4
|
|
|
5
5
|
## Overview
|
|
6
6
|
|
|
@@ -9,19 +9,19 @@ A STDIO bridge for connecting to WordPress sites via the Model Context Protocol
|
|
|
9
9
|
## Installation
|
|
10
10
|
|
|
11
11
|
```bash
|
|
12
|
-
npm install -g @
|
|
12
|
+
npm install -g @websamurai/mcp-wp-remote
|
|
13
13
|
```
|
|
14
14
|
|
|
15
15
|
Or use directly with npx:
|
|
16
16
|
|
|
17
17
|
```bash
|
|
18
|
-
npx @
|
|
18
|
+
npx @websamurai/mcp-wp-remote <url> <api-key>
|
|
19
19
|
```
|
|
20
20
|
|
|
21
21
|
## Requirements
|
|
22
22
|
|
|
23
23
|
- Node.js (ES modules support required)
|
|
24
|
-
- WordPress site with
|
|
24
|
+
- WordPress site with websamurai plugin installed
|
|
25
25
|
- Valid API key from your WordPress installation
|
|
26
26
|
|
|
27
27
|
## Usage
|
|
@@ -36,7 +36,7 @@ mcp-wp-remote <url> <api-key>
|
|
|
36
36
|
- `<url>` - Your WordPress site URL (e.g., `https://example.com`)
|
|
37
37
|
- `<api-key>` - API key for authentication (Bearer token)
|
|
38
38
|
|
|
39
|
-
The endpoint path `/wp-json/
|
|
39
|
+
The endpoint path `/wp-json/websamurai/v1/mcp` is automatically appended to the URL if not present.
|
|
40
40
|
|
|
41
41
|
### Example
|
|
42
42
|
|
|
@@ -47,7 +47,7 @@ mcp-wp-remote https://mysite.com my-secret-api-key
|
|
|
47
47
|
Or with the full endpoint:
|
|
48
48
|
|
|
49
49
|
```bash
|
|
50
|
-
mcp-wp-remote https://mysite.com/wp-json/
|
|
50
|
+
mcp-wp-remote https://mysite.com/wp-json/websamurai/v1/mcp my-secret-api-key
|
|
51
51
|
```
|
|
52
52
|
|
|
53
53
|
### As MCP Server Configuration
|
|
@@ -133,9 +133,9 @@ The bridge handles various error scenarios:
|
|
|
133
133
|
|
|
134
134
|
## WordPress Setup
|
|
135
135
|
|
|
136
|
-
1. Install the
|
|
136
|
+
1. Install the websamurai plugin on your WordPress site
|
|
137
137
|
2. Generate an API key in the plugin settings
|
|
138
|
-
3. Ensure the REST API endpoint is accessible at `/wp-json/
|
|
138
|
+
3. Ensure the REST API endpoint is accessible at `/wp-json/websamurai/v1/mcp`
|
|
139
139
|
|
|
140
140
|
## Development
|
|
141
141
|
|
|
@@ -164,10 +164,10 @@ MIT
|
|
|
164
164
|
|
|
165
165
|
## Author
|
|
166
166
|
|
|
167
|
-
|
|
167
|
+
websamurai Team
|
|
168
168
|
|
|
169
169
|
## Support
|
|
170
170
|
|
|
171
171
|
For issues and questions:
|
|
172
|
-
- WordPress Plugin: [
|
|
172
|
+
- WordPress Plugin: [WebSamurai](https://www.websamurai.io)
|
|
173
173
|
- GitHub Issues: Report issues in the repository
|
package/index.js
CHANGED