by sigmadev 0 (0 reviews)

Sigma MCP Connector

Name: Sigma MCP Connector
Author: sigmadev

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 #66,810 among WordPress.org plugins with 0+ active installations, is #1,407 of 1,659 in the Authentication category, and was last updated Oct 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.1.0 Current Version v1.1.0

Updated 2 weeks ago Last Update on 21 Oct, 2026

Refreshed 1 week ago Last Refreshed on

#1,407 of 1,659 in Authentication Downloads -69.8% this week Actively maintained

View on WordPress.org

Rank

#66,810

— No change

Active Installs

-100%

KW Avg Position

4 worse

Downloads

757

+1 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 10%

0+ 10+

39,242

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 9 more installs to reach 10+

Rank Changes

Current #66,810

Change

Best #

Upgrade to Pro

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

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

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%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.1.0
Last Updated: Oct 21, 2026
Requires WP: 6.0+
Tested Up To: 7.1.4
PHP Version: 8.0 or higher
Author: sigmadev

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

AI Claude codex mcp oauth

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,015

WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More

5M+ installs

Wordfence Security – Firewall, Malware Scan, and Login Security

Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention

All-In-One Security (AIOS) – Security and Firewall

MainWP Child – Securely Connects to the MainWP Dashboard to Manage Multiple Sites

700K+ installs

#86

View all Authentication plugins

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.