Connect an MCP client to Secure MCP

Secure MCP is available at a single endpoint: https://api.wpvip.com/mcp. The VIP MCP and WordPress MCP toolsets are both accessed through this endpoint; neither has its own endpoint. Connect any Model Context Protocol (MCP)-compatible client once via a browser-based OAuth authorization. The client handles token refresh automatically thereafter.

Which tools an agent can use in a session depends on the Secure MCP configuration: An Org admin must have activated Global MCP for the organization, and an Org or App admin must have enabled the relevant toolset for the application.

Prerequisites

• A VIP Dashboard account with at least one role on at least one organization (the agent’s token inherits the permissions of the authorizing user).
• Secure MCP activated for the organization, with at least one toolset enabled for the application the agent will operate on.
• A supported MCP client locally installed.
• The ability to open a browser on the client machine (required for the OAuth consent step).

Most clients connect through the @automattic/mcp-wordpress-remote bridge, which handles the OAuth flow against the Secure MCP endpoint. The server name (vip-platform below) is a local label; choose any name.

Claude Desktop

1. Open Claude Desktop Settings > Developer > Edit Config.
2. Add an entry under mcpServers:

{
  "mcpServers": {
    "vip-platform": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote"],
      "env": {
        "WP_API_URL": "https://api.wpvip.com/mcp",
        "OAUTH_ENABLED": "true"
      }
    }
  }
}

1. Save and restart Claude Desktop.
2. The first tool call opens a browser window for OAuth. Log in to the VIP Dashboard if prompted and select Authorize.

In some cases, the latest version of the bridge must be pinned explicitly. Use @automattic/mcp-wordpress-remote@latest in place of @automattic/mcp-wordpress-remote.

Claude Code

From a terminal, add the server:

claude mcp add vip-platform -s user \
    -e WP_API_URL=https://api.wpvip.com/mcp \
    -e OAUTH_ENABLED=true \
    -- npx -y @automattic/mcp-wordpress-remote

The -s user scope registers the server for the user account rather than the current project. Claude Code launches the OAuth flow in the default browser on the first request. Approve the authorization request in the VIP Dashboard.

To verify the connection is established:

claude mcp list

The vip-platform server appears in the output with a connected status.

Codex CLI

Edit ~/.codex/config.toml and add:

[mcp_servers.vip-platform]
command = "npx"
args = ["-y", "@automattic/mcp-wordpress-remote", "https://api.wpvip.com/mcp"]

The bridge handles the OAuth flow and converts Codex’s STDIO (Standard Input/Output) transport into the Streamable HTTP the server uses. The first prompt that touches a VIP tool opens a browser for authorization.

Cursor

1. Open Cursor settings > MCP > Add new global MCP server.
2. Paste the following configuration:

{
  "mcpServers": {
    "vip-platform": {
      "url": "https://api.wpvip.com/mcp"
    }
  }
}

1. Save. Cursor opens a browser for OAuth authorization.
2. Log in to the VIP Dashboard if prompted and select Authorize.

Gemini CLI

Edit ~/.gemini/settings.json and add:

{
  "mcpServers": {
    "vip-platform": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote"],
      "env": {
        "WP_API_URL": "https://api.wpvip.com/mcp",
        "OAUTH_ENABLED": "true"
      }
    }
  }
}

If the file does not exist yet, create it at that path. The Gemini desktop app does not support MCP connections; use the Gemini CLI.

Other clients

Any MCP client that supports Streamable HTTP with OAuth 2.0 and PKCE connects directly to the endpoint:

{
  "mcpServers": {
    "vip-platform": {
      "url": "https://api.wpvip.com/mcp"
    }
  }
}

Clients that only speak STDIO can use the @automattic/mcp-wordpress-remote bridge:

{
  "mcpServers": {
    "vip-platform": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote", "https://api.wpvip.com/mcp"]
    }
  }
}

Verify the connection

Ask the agent: “List my VIP applications.” A response listing applications confirms the connection is working. If an auth prompt appears instead, complete it and ask again.

To enumerate the tools available for the connected account, ask: “What tools do you have for the VIP Platform?” The agent lists the tools registered for the current user’s permissions and the toolsets enabled for the application.

Step-up verification

Some sensitive write operations require a step-up verification before the action runs. This is the same extra verification that appears in the VIP Dashboard for higher-risk changes.

Step-up may be required for actions that affect production traffic, access controls, security settings, domains, deployments, database operations, or other high-impact platform states.

What happens

1. The agent attempts a write action that requires step-up verification.
2. The action is paused.
3. The agent receives a step-up response and displays a verification link.
4. The user opens the link in a browser and completes verification.
5. The user returns to the agent and says something like: “I completed step-up. Please continue.”
6. The agent completes the original action.

The verification link is tied to the specific action being attempted. Completing step-up does not give the agent broader elevated access.

Example

Typically, the agent will display something like this when step-up verification is required:

WordPress VIP requires step-up verification before this change can be made.

The action has not run yet.

Open this link and complete verification: 

When done, tell me "I completed step-up" and I will continue.

Troubleshooting step-up verification

If the agent displays raw JSON instead of something like the above, look for a field named verificationUrl and open that URL directly.

If the agent does not continue after verification is complete:

1. Tell the agent: “I completed step-up. Continue the original action.”
2. If it still fails, retry the original request once.
3. If it still fails, contact VIP Support with the failure details.

Tokens and sessions

Tokens are tied to the authenticated VIP Dashboard user. Do not share an access token, as it carries the user’s identity and permissions.

To revoke access immediately, an Org admin should deactivate Global MCP via the Org Integrations panel — or contact VIP Support.

Troubleshoot

Authorization page does not open

The client uses a loopback URL (http://localhost:PORT/callback) for the OAuth redirect. Ensure loopback addresses are reachable from the client machine. Firewalls or network policies that block loopback connections prevent the OAuth flow from completing.

Token expired — tools return authentication errors

If both the access token and refresh token have expired, reconnect the client by repeating the setup steps. The client re-registers and completes a new OAuth flow automatically on the next connection attempt.

Expected tools are missing after connecting

Secure MCP only registers tools the authenticated user has permission to use from the toolsets enabled for the application. If an expected tool is not available, verify that Secure MCP is active, that the relevant toolset is enabled for the application, and that the user’s Org and App roles are correct in the People panel.