Repository navigation
Point long-form docs at docs.mainwp.com/mcp-server - #53
Conversation
The user documentation now lives on the MainWP docs site (docs.mainwp.com/mcp-server, mainwp/docs PR #99). The README shrinks from 969 to about 170 lines: per-client installation blocks, the per-tool catalog, the confirmation-flow deep dive, and the token-usage section become links to their canonical pages. The environment-variable table is now complete (21 variables, previously 17 of 21) and matches the docs-site configuration reference; the Contributing section notes the two are maintained in parallel. docs/configuration.md, security.md, troubleshooting.md, and example-prompts.md become stubs linking to their docs-site pages so existing inbound links keep resolving. docs/acceptance-testing.md is unchanged; it is contributor material and stays repo-only.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe README is shortened and reorganized around onboarding, configuration, tools, and safety. Detailed configuration, prompt, security, and troubleshooting content is replaced with links to MainWP documentation. ChangesDocumentation consolidation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 23: Update the README statements about destructive operations and
confirmation to say that, by default, operations classified as destructive
require user confirmation, reflecting the MAINWP_REQUIRE_USER_CONFIRMATION
setting and annotation-based classification without implying an unconditional
guarantee.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 600ee406-e6f9-4440-9ad3-ff24f1618b48
📒 Files selected for processing (5)
README.mddocs/configuration.mddocs/example-prompts.mddocs/security.mddocs/troubleshooting.md
Confirmation applies by default and can be disabled with MAINWP_REQUIRE_USER_CONFIRMATION=false, and destructiveness is annotation-classified rather than limited to deletions. Say so instead of implying an unconditional guarantee.
What changed
User documentation moved to a dedicated section on the docs site (https://docs.mainwp.com/mcp-server/overview, shipped in mainwp/docs#99). This PR makes the repo point there instead of duplicating it.
MAINWP_RATE_LIMIT,MAINWP_REQUEST_TIMEOUT,MAINWP_MAX_RESPONSE_SIZE,MAINWP_MAX_SESSION_DATAwere only in docs/configuration.md). It matches the docs-site configuration reference, and Contributing notes the two are maintained in parallel.No code changes.
Verification
npm run format:check,npm run lint,npm test(664 passed),npm run buildall passSummary by CodeRabbit
settings.json; improved SSL verification warning text.