MainWP MCP Server

mainwp_plugins_deactivate

Deactivate one or more plugins on a WordPress site by site ID or domain. Specify plugin slugs and optionally simulate the operation with a dry run.

Instructions

Deactivate one or more plugins on a WordPress site

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "plugins": "<plugins>"
    },
    "name": "mainwp_plugins_deactivate"
  }
}

Input Schema

Name	Required	Description
`site`	Yes	Site ID (number) or domain name (e.g., "1" or "pavinglist.com")
`dry_run`	No	Simulate the operation without making changes (defaults to MAINWP_ENABLE_DRY_RUN_BY_DEFAULT)
`plugins`	Yes	Plugin slug(s) to deactivate, comma-separated

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It does not disclose reversibility, permission requirements, side effects, or what happens to plugin settings. Minimal behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no redundancy. Front-loaded with verb and resource. Could be expanded but remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple action with well-documented parameters. Missing usage guidelines and behavioral details, but covers basic function.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 3 parameters. The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states verb 'deactivate', resource 'plugins', and scope 'on a WordPress site'. It uniquely identifies the tool among siblings like mainwp_plugins_activate and mainwp_plugins_delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use or avoid this tool. No mention of prerequisites, consequences, or comparisons with sibling tools. The description merely states the action without context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server