Title: Mumega MCP
Author: Mumega MCP
Published: <strong>Июль 29, 2026-ж.</strong>
Last modified: Июль 29, 2026-ж.

---

Плагиндерди издөө

![](https://ps.w.org/mumega-mcp/assets/icon-256x256.png?rev=3627500)

# Mumega MCP

 Автору [Mumega MCP](https://profiles.wordpress.org/mumega/)

[Жүктөө](https://downloads.wordpress.org/plugin/mumega-mcp.3.4.14.zip)

 * [Кенен маалымат](https://ky.wordpress.org/plugins/mumega-mcp/#description)
 * [Сын-пикирлер](https://ky.wordpress.org/plugins/mumega-mcp/#reviews)
 *  [Орнотуу](https://ky.wordpress.org/plugins/mumega-mcp/#installation)
 * [Development](https://ky.wordpress.org/plugins/mumega-mcp/#developers)

 [Колдоо](https://wordpress.org/support/plugin/mumega-mcp/)

## Сүрөттөө

Mumega MCP gives a site owner’s configured MCP client a small authenticated interface
to WordPress. The retained tools cover site information, posts, pages, individual
drafts, local media, categories, and tags. Media can be uploaded from multipart 
form data or base64 content supplied by the client.

Security and authority:

 * API keys are stored as password hashes, bound to an explicit existing WordPress
   user, and shown in plaintext only once.
 * All usable API keys have non-empty scopes. A key may allow read, write, or admin
   authority according to its stored scope list.
 * New post and page content is created as a draft by default.
 * Publishing, private-content mutation, and draft deletion require the stronger
   admin scope and the corresponding WordPress user permissions.
 * Request limits are enforced locally. Optional metadata-only activity logging 
   stores tool, status, duration, key ID, and time, but not request arguments or
   response content. Retention is configurable.

Setup & Keys requires a non-empty label, selected non-empty scopes, and selected
non-empty tool categories. A key created there is bound to the current explicit 
WordPress user. Direct REST child-key creation inherits the authenticated parent
key’s explicit existing WordPress-user owner. REST child-key scopes are required;
tool categories are optional, and empty tool categories mean all retained categories.

Privacy and data flow:

There are no plugin-initiated outbound requests, no telemetry, and no contact with
Mumega. Authenticated responses travel from WordPress to the MCP client configured
by the site owner. That client may send the response to an AI or other provider 
chosen and configured by the site owner; the plugin does not select or contact that
provider.

The WordPress.org directory edition cannot write PHP, JavaScript, or CSS; edit plugin
or theme files; install or update software; or self-update.

## Орнотуу

 1. Install Mumega MCP from WordPress.org and activate it.
 2. Open **Mumega MCP > Setup & Keys**.
 3. Enter a label, select the minimum scopes and tool categories needed, and create
    a key.
 4. Copy the key when it is displayed. It cannot be recovered later.
 5. Configure the site owner’s MCP client with `SITE_URL/wp-json/mcpwp/v1/mcp` and 
    send the key in the `X-API-Key` header.

## FAQ.KG

### Where are API keys stored?

Each key is stored in WordPress as a password hash and is bound to the existing 
WordPress user who created it. The plaintext is displayed only once. A user with
the Mumega MCP settings capability can revoke an active key from Setup & Keys.

### What do the scopes mean?

Read permits non-mutating operations. Write permits retained content, media, and
taxonomy mutations that the bound WordPress user is allowed to perform. Admin is
the stronger scope required for sensitive operations such as publishing, private-
content mutation, and delete operations on individual drafts. Tool-category selection
narrows which groups of tools the key can call.

### Does the plugin send data to an external service?

No plugin-initiated outbound request is made. The plugin sends authenticated results
only to the MCP client chosen by the site owner. Any provider processing performed
by that client is controlled by the owner’s client configuration, outside this plugin.

### What is stored in the activity log?

When local logging is enabled, the plugin stores tool name, status code, duration,
API-key ID, and time. It does not store request arguments or response content. The
site owner controls retention in Settings.

## Сын-пикирлер

There are no reviews for this plugin.

## Contributors & Developers

“Mumega MCP” is open source software. The following people have contributed to this
plugin.

Мүчөлөрү

 *   [ Mumega MCP ](https://profiles.wordpress.org/mumega/)

[Translate “Mumega MCP” into your language.](https://translate.wordpress.org/projects/wp-plugins/mumega-mcp)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/mumega-mcp/), check
out the [SVN repository](https://plugins.svn.wordpress.org/mumega-mcp/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/mumega-mcp/) by 
[RSS](https://plugins.trac.wordpress.org/log/mumega-mcp/?limit=100&mode=stop_on_copy&format=rss).

## Өзгөртүүлөр

#### 3.4.14

 * Security and stability hardening pass.
 * Load wp-admin/includes/media.php only for audio and video uploads, immediately
   before the metadata function that needs it; image uploads no longer load it at
   all.
 * Add an explicit permission_callback literal at every REST route registration 
   so authorization is visible to static analysis.
 * Authenticate before any resource existence check in REST permission callbacks.
 * Remove the mcpwp_manage_settings capability from the API agent role.
 * Load only the current-namespace API keys; the legacy cross-prefix key path has
   been removed from this edition.

#### 3.4.13

 * Default Setup & Keys selections include read and write access for draft-first
   content testing.

#### 3.4.3

 * Reduce the directory edition to 17 authenticated MCP tools and 19 REST route 
   patterns for content, local media, taxonomy, and local administration.
 * Keep four minimal administration pages: Setup & Keys, Tool Inventory, Settings,
   and Activity.
 * Remove remote, commercial, code-editing, and software-management surfaces.

## Мета

 *  Нуска **3.4.14**
 *  Акыркы жаңыртуу **3 ай мурун**
 *  Активдүү орнотуулар **Fewer than 10**
 *  WordPress нускасы ** 6.1 же андан жогору **
 *  Tested up to **7.0.7**
 *  PHP нускасы ** 7.4 же андан жогору **
 *  Тил
 * [English (US)](https://wordpress.org/plugins/mumega-mcp/)
 * Тег:
 * [AI](https://ky.wordpress.org/plugins/tags/ai/)[automation](https://ky.wordpress.org/plugins/tags/automation/)
   [content](https://ky.wordpress.org/plugins/tags/content/)[mcp](https://ky.wordpress.org/plugins/tags/mcp/)
   [media](https://ky.wordpress.org/plugins/tags/media/)
 *  [Advanced View](https://ky.wordpress.org/plugins/mumega-mcp/advanced/)

## Рейтинг

Азырынча эч кандай сын-пикир жок.

[Your review](https://wordpress.org/support/plugin/mumega-mcp/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/mumega-mcp/reviews/)

## Мүчөлөрү

 *   [ Mumega MCP ](https://profiles.wordpress.org/mumega/)

## Колдоо

Комментарийлер барбы? Жардам керекпи?

 [Колдоо форумун көрүү](https://wordpress.org/support/plugin/mumega-mcp/)