# MainWP (npm · @mainwp/mcp)

Manage WordPress sites in MainWP from AI tools, with approval before destructive changes by default.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `@mainwp/mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/mainwp-mainwp-mcp/mainwp-mcp.md), [page](https://verifymcp.io/servers/mainwp-mainwp-mcp/mainwp-mcp)

## Channel facts

- Registry: `npm`
- Package: `@mainwp/mcp`
- Version: `1.5.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (GPL-3.0).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 466 tokens (~233/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the MainWP MCP server?

MainWP runs locally as an npm package, launched with npx -y @mainwp/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add mainwp-mainwp-mcp -- npx -y @mainwp/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mainwp-mainwp-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mainwp/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mainwp-mainwp-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mainwp/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mainwp-mainwp-mcp -- npx -y @mainwp/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mainwp-mainwp-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mainwp/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mainwp-mainwp-mcp --command npx --arg -y --arg @mainwp/mcp
```

### Hermes

```yaml
mcp_servers:
  mainwp-mainwp-mcp:
    command: "npx"
    args: ["-y", "@mainwp/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mainwp-mainwp-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mainwp/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mainwp-mainwp-mcp -t stdio -c npx -a -y @mainwp/mcp
```

### Other

```json
{
  "mcpServers": {
    "mainwp-mainwp-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mainwp/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-14 (score 69, +30)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-10-13 (score 39, 0)

- [functional] Package version: 1.5.0 → 1.5.1

### 2026-10-12 (score 39, +1)

- [functional improvement] Security disclosure: unverified → pass

### 2026-10-11 (score 38)

First indexed and scored.

## MCP tools (2)

### `mainwp_get_setup_status` (~82 tokens)

Report whether the MainWP MCP server is connected to a Dashboard yet, and return the setup instructions to show the user. Call this first when MainWP tools are missing. If the server has credentials but could not reach the Dashboard, this retries the connection. If the Dashboard rejected the credentials, this reports which user was rejected and where each value came from.

### `mainwp_configure` (~133 tokens)

Connect this server to a MainWP Dashboard using credentials the user supplied in chat. Requires all three values at once. The credentials are verified against the Dashboard, then saved to ~/.config/mainwp-mcp/settings.json on this machine with owner-only permissions; the password is scrubbed from server logs and never echoed back. Only usable before the server is connected.

Input parameters:

- `application_password` (string, required): WordPress Application Password for that user
- `dashboard_url` (string, required): HTTPS URL of the MainWP Dashboard, for example https://dashboard.example.com
- `username` (string, required): WordPress admin username on the Dashboard

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mainwp-mainwp-mcp/mainwp-mcp#diagnostics

## Score history

- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 69
- 2026-10-14: 69
- 2026-10-13: 39
- 2026-10-12: 39
- 2026-10-11: 38

## Common questions

### What is the MainWP MCP server?

MainWP is an MCP server listed in the public MCP registry as io.github.mainwp/mainwp-mcp. Manage WordPress sites in MainWP from AI tools, with approval before destructive changes by default. This page covers its npm package (@mainwp/mcp).

### Is the MainWP MCP server safe to use?

MainWP scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MainWP MCP server expose?

MainWP exposes 2 tools: mainwp_get_setup_status, mainwp_configure. Their descriptions and schemas cost roughly 215 tokens of context every time the server is loaded.

### Is the MainWP MCP server still maintained?

MainWP is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the MainWP MCP server under?

MainWP declares the GPL-3.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@mainwp/mcp
- Socket report: https://socket.dev/npm/package/@mainwp/mcp
- Repository: https://github.com/mainwp/mainwp-mcp
- Website: https://docs.mainwp.com/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/mainwp-mainwp-mcp/mainwp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mainwp-mainwp-mcp/mainwp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mainwp-mainwp-mcp/mainwp-mcp