Someone reports a typo on your WordPress site through Marker.io. Instead of switching between tabs, your AI tool reads the issue and fixes the content directly in WordPress. This guide shows how to connect both Marker.io MCP and WordPress MCP to the same AI tool.

What you can do

When both servers are connected, your AI tool can:

Read Marker.io issues, screenshots, properties, and technical context
Update WordPress posts, pages, and media
Fix typos, broken links, and outdated content from a single prompt
Mark issues as resolved in Marker.io when the fix is done

For a full list of Marker.io MCP tools, see MCP Integration (Model Context Protocol).

Before you start

A Marker.io account with at least one website project
Marker.io MCP connected to your AI tool. Follow MCP setup guides if you haven't done this yet.
A WordPress site (WordPress.com or self-hosted WordPress.org)
An MCP-compatible AI tool (Claude Code, Cursor, VS Code, or similar)

Which WordPress do you have? If your admin URL starts with wordpress.com, you're on WordPress.com. If it uses your own domain followed by /wp-admin, you're on self-hosted WordPress.org.

WordPress.com setup

WordPress.com has built-in MCP support. No plugin needed.

Enable MCP access

Go to wordpress.com/me/mcp
Enable MCP access for your account
Note the server URL: https://public-api.wordpress.com/wpcom/v2/mcp/v1

WordPress.com uses OAuth. Your AI tool will open a browser window to authorize access. See WordPress.com MCP documentation for details.

Add to your AI tool

Example for Claude Code

claude mcp add --transport http marker-io https://connect.marker.io/mcp
claude mcp add --transport http wordpress https://public-api.wordpress.com/wpcom/v2/mcp/v1

Using a different AI tool? See MCP setup guides for Marker.io and add the WordPress server URL alongside it.

WordPress.org (self-hosted) setup

Self-hosted WordPress sites need the MCP Adapter plugin and an Application Password for authentication.

Install the MCP adapter

In your WordPress admin, go to Plugins > Add New
Search for MCP Adapter
Click Install Now, then Activate
Go to Users > Profile and scroll to Application Passwords
Enter a name (e.g. "AI tool") and click Add New Application Password
Copy the generated password. You will not see it again.

WordPress 6.9 and later includes MCP support built in. Skip step 1-3 if you're on 6.9+. See the WordPress MCP Adapter documentation for details.

Add to your AI tool

Replace your-site.com with your WordPress domain. Replace YOUR_APPLICATION_PASSWORD with the password from step 6.

Example for Claude Code

claude mcp add --transport http marker-io https://connect.marker.io/mcp
claude mcp add --transport http wordpress https://your-site.com/wp-json/mcp/v1 --header "Authorization: Bearer YOUR_APPLICATION_PASSWORD"

Using a different AI tool? See MCP setup guides for Marker.io and add the WordPress server URL alongside it.

Workflow: fix a content issue

Here's what a typical workflow looks like once both servers are connected.

A reporter submits an issue in Marker.io: "Typo on the About page - 'recieve' should be 'receive'."
In your AI tool, ask: "List open issues from Marker.io."
The AI reads the issue details and screenshot.
Ask: "Fix the typo mentioned in this issue on WordPress."
The AI finds the About page in WordPress and updates the content.
Ask: "Mark the Marker.io issue as resolved."

That's it. No tab switching, no copy-pasting.

Tips

You can ask the AI to handle multiple issues in a single prompt.
The AI can read Marker.io screenshots to understand visual context, not just text descriptions.
For code-level bugs (not content), pair Marker.io MCP with your code editor instead of WordPress MCP.
To install the Marker.io reporting widget on your WordPress site, see WordPress Plugin.