WPMission MCP Server

io.github.support-wpmissionPublished by GitHub account support-wpmissionv0.1.0Updated Oct 24, 2026

WPMission MCP server for WordPress management product information.

Overview

AI-generated overview

Provides an assistant with static product information about the WPMission WordPress management platform.

What you can do
The server exposes a single tool, wpmission_info, which returns information about WPMission and its WordPress website management platform. It runs locally over stdio and is distributed as a Docker image on GHCR. The README states that live WordPress management operations are not yet connected, so the server only serves descriptive product information.
When to use it
Worth adding only if you want an assistant to answer questions about what WPMission is and what its WordPress management platform offers. It is not useful for actually managing WordPress sites, since those operations are not connected.
Requirements
Runs as a local stdio process. Either Docker installed on the machine, or Node.js with npm to run from source. No accounts, API keys, environment variables, or headers are declared.
Before you install
No credentials or secrets are requested and no write, send, or delete actions are described. The server only returns product information, so there is little risk beyond the usual caution of running a third-party container image.

Installation

In SourceWeft

  1. Open WPMission MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

WPMission MCP Server

Connect WPMission with AI assistants using the Model Context Protocol (MCP).

WPMission is a platform designed to help WordPress developers, freelancers, and agencies manage multiple WordPress websites from a single dashboard.

Overview

The WPMission MCP Server provides an MCP-compatible interface for AI assistants.

Current Version: 0.1.0

Status: Published on the Official MCP Registry

Current Features

  • MCP protocol integration
  • WPMission product information tool
  • Docker container support
  • Standard input/output (stdio) transport
  • GitHub Actions automated testing
  • Public container image on GHCR

Available MCP Tool

wpmission_info

Returns information about WPMission and its WordPress website management platform.

Note: Live WordPress management operations are not yet connected.

Installation

Option 1: Docker

Docker must be installed on your computer.

bash
docker run --rm -i ghcr.io/support-wpmission/wpmission-mcp-server:0.1.0

Option 2: Run from Source

Clone the GitHub repository:

bash
git clone https://github.com/support-wpmission/wpmission-mcp-server.gitcd wpmission-mcp-servernpm installnpm start

MCP Client Configuration

For MCP clients supporting local stdio servers, use the following example configuration:

json
{  "mcpServers": {    "wpmission": {      "command": "docker",      "args": [        "run",        "--rm",        "-i",        "ghcr.io/support-wpmission/wpmission-mcp-server:0.1.0"      ]    }  }}

Configuration locations vary between MCP clients.

Development Roadmap

Planned improvements include:

  • WPMission REST API integration
  • WordPress website status monitoring
  • Multi-site management tools
  • Additional MCP actions and triggers

These features are not available in version 0.1.0.

Project Links

Feedback and Support

For bug reports, feature requests, or technical questions, open an issue:

https://github.com/support-wpmission/wpmission-mcp-server/issues

Maintainer

WPMission Team

https://wpmission.com

Version

0.1.0 — Initial MCP Server release.

Source: README.md at commit 7d8bd34

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 13, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.