Sigma MCP Connector
by sigmadev 0 (0 reviews)

Sigma MCP Connector

Turn WordPress into a secure, role-scoped MCP server so Claude, Codex, VS Code, and Cursor AI can read and edit content via OAuth 2.0.

Sigma MCP Connector ranks #53,985 among WordPress.org plugins with 0+ active installations, is #1,409 of 1,585 in the Authentication category, and was last updated Sep 7, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.5 (Current: 7.1.1)
v1.0.0 Current Version v1.0.0
Updated 1 week ago Last Update on 07 Sep, 2026
Refreshed 10 hours ago Last Refreshed on
#1,409 of 1,585 in Authentication Downloads -12.9% this week Actively maintained
View on WordPress.org
Rank
#53,985
No change
Active Installs
0+
-4%
KW Avg Position
121
No change
Downloads
271
+16 today
Support Resolved
0%
No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 10

Total Progress 30%
0+ 10+
28,499
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
Upgrade to Pro
Need 7 more installs to reach 10+

Rank Changes

50,278 53,472 56,667 59,861 63,055 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026
46,838 52,614 58,391 64,168 69,944 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026
Current #53,985
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

10 20 30 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026
10 20 30 40 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0
0 reviews
Overall 0%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Sigma MCP Connector

No, not automatically. Sigma MCP Connector does not make outbound connections to any AI provider and does not phone home for analytics, licensing, or updates. It works the other way around: it turns your own WordPress site into an MCP server that a client you explicitly register can connect into — and only after a logged-in WordPress user explicitly approves an OAuth consent screen naming that specific client. From that point on, every request runs as that WordPress user, restricted to their existing WordPress role and capabilities, and is written to the Activity Log.
Exactly what the authorizing WordPress user's role allows — nothing more. Every one of the 27 tools is checked with current_user_can() against a specific WordPress capability on every single call, not just at connection time. Revoke the user's role, or revoke the token from the Connections page, and access stops immediately.
OAuth client registrations, tokens, and the activity log are stored in five plugin-owned database tables on your own WordPress database — nothing is sent off-site. You control log retention (or disable it) from the Activity Log screen.
Any MCP-aware client that supports OAuth 2.0 Authorization Code + PKCE — Claude.ai, Claude Desktop, Codex, VS Code (GitHub Copilot), and Cursor AI are documented in detail on the plugin's Documentation screen, with copy-paste config examples for each.
Yes. Deactivate or delete an OAuth client, or revoke an individual token or all tokens for a user, from Sigma MCP → Connections — access is checked on every request, so revocation takes effect immediately.
It works over HTTP for local development, but HTTPS is strongly recommended (and the admin screen will warn you) in production, since OAuth access and refresh tokens should never travel unencrypted.
Deactivating stops the OAuth/MCP endpoints and clears the scheduled log-purge cron job, but does not delete any data. Uninstalling (deleting) the plugin removes its database tables, options, and transients.

Sign In / Register

You need to sign in or register to use this feature.