Why is the API returning a 404 error?

You must enable 'Pretty Permalinks' in your WordPress Dashboard (Settings > Permalinks). The REST API will not function with the 'Plain' setting.

How do I find my API Token?

In your MainWP Dashboard, navigate to Settings > REST API and create a new API Key with 'Write' permissions. Your token is encrypted at rest and injected securely at runtime.

Can I update plugins across all sites?

Yes, the `upgrade_site_resource` tool can target specific resources across the entire network by providing the necessary parameters in the JSON body.

MainWP MCP Server for VS Code Copilot 8 tools — connect in under 2 minutes

Name: MainWP
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 8 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install MainWP and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "mainwp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About MainWP MCP Server

Connect your MainWP Dashboard to any AI agent to automate your WordPress network management. This MCP server enables your agent to list child sites, monitor pending updates for core, plugins, and themes, and trigger security scans directly from natural language interfaces.

GitHub Copilot Agent mode brings MainWP data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Network Oversight — List all managed child sites and retrieve real-time status and update counts
Update Management — Query all pending WordPress core, plugin, and theme upgrades across your entire network
Automated Sync — Trigger a global synchronization to fetch the latest data from all connected sites instantly
Security Auditing — Initiate vulnerability scans and malware checks using configured MainWP extensions
Inventory Control — List all plugins and themes installed on any specific child site for auditing
One-Click Upgrades — Execute resource upgrades programmatically to maintain network-wide security

The MainWP MCP Server exposes 8 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect MainWP to VS Code Copilot via MCP

Follow these steps to integrate the MainWP MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using MainWP

Ask Copilot: "Using MainWP, help me...". 8 tools available

Why Use VS Code Copilot with the MainWP MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with MainWP through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

MainWP + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the MainWP MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

MainWP MCP Tools for VS Code Copilot (8)

These 8 tools become available when you connect MainWP to VS Code Copilot via MCP:

get_pending_updates_count

Get a quick count of all pending updates

list_available_updates

List all pending core, plugin, and theme updates

list_child_sites

List all connected WordPress sites

list_site_plugins

List all plugins installed on a specific site

scan_network_malware

Trigger a malware scan across the network

scan_network_vulnerabilities

Trigger a vulnerability scan across the network

sync_child_sites

Trigger a synchronization with all child sites

upgrade_site_resource

Requires a JSON body with details. Execute an upgrade for a specific plugin or theme

Example Prompts for MainWP in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with MainWP immediately.

"List all connected child sites in MainWP."

"How many pending updates are available across my network?"

"Run a vulnerability scan across all sites."

Troubleshooting MainWP MCP Server with VS Code Copilot

Common issues when connecting MainWP to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

MainWP + VS Code Copilot FAQ

Common questions about integrating MainWP MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.