by
Rectus Inc.
1 (0 reviews)
Rectus Content Access for MCP
Connect MCP clients to WordPress posts, pages, custom post types, taxonomies, and media with configurable access.
Rectus Content Access for MCP ranks #60,879 among WordPress.org plugins with 1+ active installations, is #4,392 of 6,009 in the Media category, a 1/5 rating from 0 reviews, and was last updated Jul 25, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7
v0.5.3
Current Version v0.5.3
Updated 4 days ago
Last Update on 25 Jul, 2026
Refreshed 6 hours ago
Last Refreshed on
#4,392 of 6,009 in Media
Actively maintained
Rank
#60,879
—
No change
Active Installs
1+
—
No change
KW Avg Position
84
3 worse
Downloads
124
+2 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
60,100
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 9 more installs to reach 10+
Rank Changes
Current
#60,879
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 1 of 1| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| mcp | 84 | — | Tag | 14 hours ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.5.3
- Last Updated
- Jul 25, 2026
- Requires WP
- 6.9+
- Tested Up To
- 7
- PHP Version
- 7.4 or higher
- Author
- Rectus Inc.
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
7K+ installs
#2,721
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#991
Jetpack - WP Security, Backup, Speed, & Growth
3M+ installs
#18
Advanced Custom Fields (ACF®)
2M+ installs
#28
Image Optimization - Compress Images and Convert to WebP or AVIF
1M+ installs
#60
EWWW Image Optimizer
1M+ installs
#62
Smush – Image Optimization, Compression, Lazy Load, WebP & CDN
1M+ installs
#64
Regenerate Thumbnails
1M+ installs
#65
Imagify Image Optimization: Optimize Images | Compress & Convert to WebP/AVIF
1M+ installs
#67
Smart Slider 3
800K+ installs
#78
Frequently Asked Questions
Common questions about Rectus Content Access for MCP
No service operated by the plugin author is required. MCP requests are handled by WordPress through the bundled official MCP Adapter library. When an OAuth client uses an HTTPS URL as its client ID, Rectus Content Access for MCP retrieves public client metadata from that client-provided URL as described below.
During OAuth authorization, a connecting client may provide an HTTPS metadata URL as its client ID. Rectus Content Access for MCP then sends a server-side GET request to that exact URL with an Accept: application/json header. The response is limited to 64 KB and valid metadata is cached for one hour. No WordPress content, passwords, OAuth codes, or tokens are sent. The destination is selected and operated by the connecting MCP client, not by the plugin author, so the destination operator's terms and privacy policy apply.
No. The server-side plugin runs in PHP. An MCP client may have its own local runtime requirements, depending on the client.
No. The user signs in on the WordPress site and approves the connection in the browser. The MCP client receives short-lived OAuth tokens instead of the WordPress password.
Open Settings, Rectus Content Access for MCP and revoke the connection in the OAuth connections table. MCP clients may also clear or revoke their saved authorization.
Codex and Claude Code should call the media upload ticket tool with the local image filename, byte size, MIME type, and attachment metadata. The tool returns a plugin REST endpoint and a short-lived, one-time token. The client then sends the image bytes directly as multipart form data. The image does not enter the model context, and no Application Password or second WordPress login is required. The ticket is valid for five minutes, is bound to the authorized WordPress user and expected file metadata, and is stored only as a SHA-256 hash. Repeating a completed request with the same ticket returns the existing attachment instead of creating a duplicate. MCP clients that cannot perform the direct HTTP upload may continue to use the Base64 media upload tool. Files already present in the WordPress uploads/mcp-inbox directory may use the media import tool without transferring image bytes through MCP.
Use the media list tool to search the WordPress media library and obtain the exact attachment ID and filename. Then call the media delete tool with that ID, the matching filename, and confirm set to true. WordPress checks the authorized user's delete permission for the selected attachment. Deletion is permanent and removes the attachment and its generated files. Existing links to that media in post content are not rewritten, so clients should show the selected ID and filename to the user before confirming.
Rectus Content Access for MCP derives the client configuration name from the site's domain and subdirectory path. For example, rectus.co.jp becomes wordpress-rectus-co-jp, while example.com/site-a becomes wordpress-example-com-site-a. This prevents different WordPress sites from overwriting each other's MCP client configuration.
Codex App and Codex CLI share MCP configuration. After the add command saves the server, Codex App may open the authorization screen automatically. Approve that screen once. Run codex mcp login only when authorization does not start; running both flows at the same time can create a duplicate OAuth connection.
Run the displayed claude mcp add command, then run claude mcp login. The login command opens the browser authorization screen directly, so there is no need to start Claude Code and run /mcp manually.
