MainWP MCP Server

mainwp_plugins_install

Install a plugin from WordPress.org on a specified site by providing the site ID or domain and the plugin slug. Supports dry run to simulate the operation without making changes.

Instructions

Install a plugin from WordPress.org on a 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>",
      "slug": "<slug>"
    },
    "name": "mainwp_plugins_install"
  }
}

Input Schema

Name	Required	Description
`site`	Yes	Site ID (number) or domain name (e.g., "1" or "pavinglist.com")
`slug`	Yes	Plugin slug from WordPress.org (e.g., "akismet")
`dry_run`	No	Simulate the operation without making changes (defaults to MAINWP_ENABLE_DRY_RUN_BY_DEFAULT)

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. Description does not disclose side effects (e.g., overwrites existing plugin? requires activation?), error handling, or asynchronous behavior.

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

Conciseness5/5

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

Single sentence, no fluff, front-loaded verb and resource. Highly concise for a simple action.

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

Completeness2/5

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

Missing details on installation process, success/failure response, and prerequisites. Incomplete for an agent to fully understand the tool's consequences.

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 descriptive parameter comments. 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 'install', resource 'plugin from WordPress.org', and target 'site'. Distinct from sibling tools like mainwp_plugins_activate and mainwp_themes_install.

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 guidance on when to use this tool vs alternatives (e.g., activate if already installed). No mention of prerequisites like site being connected or slug validity.

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

Deploy Server