Understanding MCP Servers in WordPress: Tools, Resources, and Prompts

👁 5 views

What is a Model Context Protocol (MCP) Server?

Imagine you have a super-smart assistant (like Claude) who can help you with your work, but that assistant can’t actually do anything in your systems—it can only talk to you. The Model Context Protocol (MCP) is like giving your AI assistant hands, eyes, and a library card.

MCP is an open standard developed by Anthropic that creates a bridge between AI assistants and the tools they need to help you. Think of it as a universal adapter that lets Claude (or any AI) safely interact with your WordPress site, your files, your databases, or any other system—without you having to copy-paste information back and forth.

An MCP Server sits between Claude and your WordPress installation, exposing specific capabilities in a standardized way. Instead of you manually describing what needs to happen, Claude can directly see what’s possible and take action with your approval.

The Three Core Building Blocks: Tools, Resources, and Prompts

MCP organizes its capabilities into three distinct types, each designed for different kinds of interactions. In this WordPress implementation, we call the executable functions “Abilities,” which correspond to what MCP formally calls “Tools.”

1. Tools (Called “Abilities” in This Implementation): The AI’s Hands

What They Are: Tools are actions the AI can perform. They’re model-controlled, which means Claude can discover them and decide when to use them based on what you’re asking for. Think of them as giving Claude hands to actually do things.

Everyday Analogy: Imagine asking your assistant to “organize my office.” With tools, the assistant can:

• Open filing cabinets (read your posts)
• Create new folders (create categories)
• Move documents (update content)
• Shred old papers (delete drafts)
• Label everything properly (add metadata)

The Important Safety Feature: You always have final approval. When Claude wants to use a tool to change something important, you’ll see a clear confirmation prompt. It’s like your assistant asking “Should I really delete these 50 old draft posts?” before taking action.

Real WordPress Examples from This Implementation (133 Total Abilities):

• Content Management: “Create a blog post about summer recipes” → Claude uses wp-mcp-core/create-post to write and format the post
• E-Commerce Operations: “We just got 50 more units of the blue sweater in stock” → Claude uses wp-mcp-wc/update-stock to update inventory
• Site Organization: “Make a new category called ‘Customer Stories’” → Claude uses wp-mcp-core/create-category
• Bulk Operations: “Add a holiday sale banner to all product pages” → Claude uses multiple tools in sequence to update hundreds of pages

The Power of Tools: With 133 available abilities across Core WordPress (79), WooCommerce (10), ACF (34), and Blockhead (10) integrations, Claude can manage nearly every aspect of a WordPress site. The key is that Claude automatically knows when to use each one based on what you ask for.

2. Resources: The AI’s Reference Library

What They Are: Resources are information sources that help Claude understand your specific setup. They’re application-driven, which means you (or the app) decide what information to make available. Resources don’t do anything—they just provide context. Think of them as giving Claude eyes to see your site’s blueprints.

Everyday Analogy: Imagine hiring someone to redecorate your house. Resources are like giving them:

• Your paint color swatches (brand colors)
• Measurements of each room (site structure)
• Photos of furniture you already own (existing content patterns)
• Your style preferences written down (design guidelines)
• A map of where everything is stored (content organization)

Without resources, they’d have to guess or keep asking questions. With resources, they know exactly what you want and what you have to work with.

Why Resources Matter: Tools tell Claude what it can do. Resources tell Claude how your specific site works. Without resources, Claude would need to guess your color palette, ACF structure, or available block patterns. With resources, Claude has your site’s documentation built right in.

How Resources Work in Practice

Resources are read-only information endpoints identified by URIs (web addresses). When Claude needs to understand something about your site before taking action, it reads the relevant resource:

• resource://wordpress/acf/schema – Complete ACF field definitions
• resource://wordpress/theme/config – Theme colors, fonts, and layouts
• resource://wordpress/blocks/patterns – Available block patterns
• resource://wordpress/site/guidelines – Your content and style rules

Detailed Resource Examples for WordPress

1. ACF Schema Resource – Your Custom Fields Blueprint

Non-Technical Example: Your WordPress site has a “Team Member” page type with specific fields: Name, Job Title, Bio, Photo, Email, and Social Links. Without a resource, you’d have to explain this structure every time. With an ACF schema resource, Claude can read the blueprint and automatically know: “Ah, when creating a team member page, I need to fill in these six specific fields in this exact format.”

What It Contains:

• All field group definitions and where they appear
• Field types (text, image, date picker, etc.)
• Validation rules (“email must be valid,” “bio max 500 characters”)
• Conditional logic (“show LinkedIn field only if ‘Has Social Media’ is checked”)

Real Conversation:

You: “Add Sarah Johnson to the team page. She’s our new marketing director.”

Claude: [Reads ACF schema resource] “I’ll create a team member page with all the required fields. I’ll need her bio, photo, email, and any social media links you’d like to include. Should I use the standard marketing director job description template?”

2. Theme Configuration Resource – Your Design System

Non-Technical Example: Your company has specific brand colors (#2C5F8D for primary, #E8927C for accents), two approved fonts (Montserrat for headings, Open Sans for body text), and standardized spacing. The theme configuration resource is like handing Claude your brand style guide.

What It Contains:

• Complete color palette with semantic names (“primary,” “secondary,” “danger”)
• Typography settings (font families, sizes, weights)
• Spacing and layout constraints
• Available template parts (headers, footers, sidebars)

Real Conversation:

You: “Create a new landing page for our spring promotion.”

Claude: [Reads theme config resource] “I’ll build that using your primary brand color (#2C5F8D) for the header, Montserrat font for the headline, and your standard button styles. Want me to use your default hero section layout or try something new?”

3. Block Pattern Library Resource – Your Reusable Layouts

Non-Technical Example: You’ve created several pre-designed sections: a “Testimonials Grid” with customer quotes, a “Product Showcase” with three columns, a “FAQ Accordion” that expands/collapses. The pattern library resource is like showing Claude your catalog of pre-built Lego sections.

What It Contains:

• Pattern names and descriptions
• Complete block markup for each pattern
• Preview images
• Usage guidelines (“Use testimonials pattern on service pages”)

Real Conversation:

You: “Add a testimonial section to the About page.”

Claude: [Reads pattern library resource] “I found your ‘Testimonials Grid’ pattern. I’ll insert it on the About page. Should I pull the latest testimonials from your reviews, or do you have specific ones you’d like featured?”

4. WooCommerce Configuration Resource – Your Store Setup

Non-Technical Example: Your online store has specific categories (“Electronics > Audio > Headphones”), shipping classes (“Standard” vs “Expedited”), and tax rules (“Digital products are tax-exempt in Oregon”). This resource is like giving Claude your store’s operations manual.

Real Conversation:

You: “Add our new wireless headphones to the store.”

Claude: [Reads WooCommerce config resource] “I’ll add it to Electronics > Audio > Headphones, assign it to the ‘Standard Electronics’ shipping class (3-5 business days), and apply standard taxable rate. Does it come in multiple colors, or just one variant?”

5. Site Documentation Resource – Your House Rules

Non-Technical Example: Your company has specific writing guidelines: “Always capitalize ‘Internet,’ keep paragraphs under 3 sentences, include at least one image per 500 words, link to related articles.” This resource is your editorial style guide.

Real Conversation:

You: “Write a blog post about our new sustainability initiative.”

Claude: [Reads documentation resource] “I’ll write that following your style guidelines: short paragraphs, optimized images, internal links to your previous environmental posts. Should I target about 800 words, which would need 2 images based on your guidelines?”

The Self-Documenting Advantage

Resources create a self-documenting WordPress environment. Instead of maintaining separate documentation that gets outdated, your site’s configuration becomes the documentation. Claude always has access to the current truth about your WordPress installation.

Especially Powerful For:

• Onboarding New Team Members: New hires (or AI assistants) instantly understand site structure without a training manual
• Maintaining Consistency: Every operation automatically uses correct field names, color values, and patterns
• Managing Multiple Sites: If you manage 10 client sites, each site’s unique configuration is clearly documented and accessible
• Preventing Errors: Claude can’t accidentally use a color that’s not in your palette or reference a field that doesn’t exist

Current Implementation Status: Resources are part of the MCP specification but not yet implemented in this WordPress MCP Server. The 133 abilities (tools) are fully functional. Adding resources would provide Claude with comprehensive site context for even more intelligent automation.

3. Prompts: Pre-Made Recipes for Common Tasks

What They Are: Prompts are pre-built, reusable workflows that you explicitly choose to run. They’re user-controlled, which means you pick them from a menu (often as “slash commands” like /create-blog-post). Think of them as giving Claude a cookbook of your best recipes for getting work done.

Everyday Analogy: Imagine you frequently need to:

• Prepare your house for guests (clean, arrange furniture, set out snacks)
• Pack for a business trip (laptop, chargers, business cards, specific documents)
• Close up your store for the night (cash register, lights, alarm, lock doors)

Instead of explaining each step every single time, you create a checklist. Prompts are like those checklists—pre-written instructions that bundle multiple steps into one command.

How You’d Use Them: You type a slash command like /launch-product or select it from a menu, Claude asks for any specific details it needs (“What’s the product name?”), then executes the entire multi-step workflow automatically.

Example WordPress Prompt Scenarios:

• “Create SEO-Optimized Blog Post” (/seo-blog-post): You provide the topic. Claude creates a post with proper headings, meta description, featured image, internal links to related posts, and schema markup—all following your SEO checklist.
• “Setup WooCommerce Product” (/new-product): You provide basic product info. Claude creates the product, adds it to correct categories, sets up shipping, configures attributes, uploads images, and creates an announcement blog post.
• “Build Landing Page” (/landing-page): You describe the purpose. Claude assembles hero section, features grid, testimonials, FAQ, and contact form using your approved patterns and brand colors.
• “Prepare Site for Sale” (/sale-prep): You specify the sale details. Claude creates sale banner, updates product prices, creates promotional blog posts, sets up sale category, and adds countdown timer.

The Efficiency Factor: Prompts transform “Let me explain what I need step by step” into “Run the product launch workflow.” They encode your company’s best practices so anyone on your team can execute them perfectly.

Current Implementation Status: Prompts are part of the MCP specification but not yet implemented in this WordPress MCP Server. Adding prompts would enable one-command execution of complex, multi-step WordPress workflows that you use frequently.

How They Work Together: Real-World Examples

Understanding Tools, Resources, and Prompts individually is valuable, but seeing how they work together in real scenarios shows the true power of MCP. Here are detailed walkthroughs showing actual conversations and what happens behind the scenes.

Example 1: Launching a New Product (Full MCP Implementation)

This example shows how all three MCP concepts would work together if fully implemented:

You Type: /launch-product (invoking a Prompt)

Claude Asks: “I’ll help you launch a new product. What’s the product name, SKU, price, and initial stock quantity?”

You Reply: “Premium Wireless Headphones, SKU WH-2024, $149, 50 units in stock”

Behind the Scenes – What Claude Does:

Step 1 – Reads Resources (Understanding Your Setup):

• Checks WooCommerce configuration: “Ah, electronics go in Electronics > Audio > Headphones, ship via ‘Standard Electronics’ (3-5 days), standard tax rate applies”
• Checks ACF schema: “Product pages need these custom fields: Battery Life, Weight, Warranty, and Technical Specifications repeater”
• Checks brand colors: “Primary blue #2C5F8D, accent coral #E8927C”

Step 2 – Prompt Guides the Workflow:

The “Launch Product” prompt contains a checklist:

• ✓ Create WooCommerce product
• ✓ Add custom specifications
• ✓ Generate and upload product images
• ✓ Write announcement blog post
• ✓ Feature on homepage
• ✓ Send team notification

Step 3 – Executes Tools (Taking Action):

Tool 1: Create the product with wp-mcp-wc/create-product

Creating product:
  Name: Premium Wireless Headphones
  SKU: WH-2024
  Price: $149.00
  Stock: 50 units
  Category: Electronics > Audio > Headphones
  Shipping: Standard Electronics
  
Result: Product created! ID #1847

Tool 2: Add specifications with wp-mcp-acf/update-field

Adding custom fields:
  Battery Life: 30 hours
  Weight: 250g
  Warranty: 2 years
  
  Technical Specs (repeater):
    - Driver Size: 40mm
    - Frequency Response: 20Hz-20kHz
    - Bluetooth: 5.0
    - Impedance: 32 ohms

Tool 3: Create announcement with wp-mcp-core/create-post

Creating blog post:
  Title: "Introducing Premium Wireless Headphones"
  Content: [AI-generated announcement highlighting features]
  Categories: Product Announcements, Audio
  Status: Published
  
Result: Post published at /blog/introducing-premium-wireless-headphones/

Tool 4: Feature on homepage with wp-mcp-core/update-option

Updating homepage:
  Adding product #1847 to featured products carousel
  Position: First (most prominent)

Claude Reports Back: “Product launched successfully! Your Premium Wireless Headphones (SKU: WH-2024) is now live with 50 units in stock at $149. I’ve published an announcement post, featured it on your homepage, and all technical specs are filled in. The product page is ready at /product/premium-wireless-headphones/”

Time Saved: 8 seconds vs. 20-30 minutes manually clicking through multiple admin screens

Example 2: Bulk Content Migration (Current Implementation)

This example uses only the Tools/Abilities currently implemented:

You Say: “I need to move all my old blog posts from the ‘News’ category to a new category called ‘Company Updates,’ and add a disclaimer to each one saying the information might be outdated.”

Claude Responds: “I’ll handle that migration for you. First, let me check what we’re working with…”

Behind the Scenes:

Tool 1: Check existing categories with wp-mcp-core/list-categories

Found: "News" category (ID: 12) with 50 posts
"Company Updates" doesn't exist yet

Tool 2: Create new category with wp-mcp-core/create-category

Creating category:
  Name: Company Updates
  Slug: company-updates
  Description: Official company announcements
  
Result: Category created with ID #24

Tool 3: Get all posts from old category with wp-mcp-core/list-posts

Fetching posts from "News" category...
Found 50 posts (IDs: 445-494)

Tool 4: Update each post (repeated 50 times with wp-mcp-core/update-post)

Processing post #445:
  - Getting current content
  - Adding disclaimer: "Note: This information was published before 2024..."
  - Changing category from #12 to #24
  - Saving changes
  
[Repeating for posts 446-494...]

Tool 5: Verify everything worked with wp-mcp-core/list-posts

Verification complete:
  "Company Updates" now has 50 posts
  All posts include disclaimer
  "News" category is now empty

Claude Reports: “Migration complete! I’ve created the ‘Company Updates’ category, moved all 50 posts from ‘News,’ and added the disclaimer to each one. All posts are now properly categorized and updated.”

Time Saved: 15 seconds vs. 2-3 hours of tedious manual work

Example 3: Emergency Inventory Update (Current Implementation)

Scenario: It’s 5 PM on Friday. A shipment just arrived at your warehouse with 25 units each of 34 different products from your Summer Collection. You need to update your online store immediately so customers can order over the weekend.

You Say: “We just got our shipment! Add 25 units to every product in the Summer Collection. Also, some were showing as out of stock—mark those as available again.”

Behind the Scenes:

Tool 1: Find all products with wp-mcp-wc/list-products

Searching for: category = "summer-collection"
  
Results:
  Total products: 34
  Out of stock: 15 products (0 units each)
  In stock: 19 products (varying quantities)

Tool 2: Update stock for each product with wp-mcp-wc/update-stock

Product #1532 "Blue Sundress":
  Old stock: 12 units
  New stock: 37 units (+25)
  Status: In stock
  
Product #1545 "White Linen Shirt":
  Old stock: 0 units (OUT OF STOCK)
  New stock: 25 units (+25)
  Status: Changed to IN STOCK ✓
  
[Continuing for all 34 products...]

Tool 3: Verify with wp-mcp-wc/list-products

Verification:
  All 34 products now show "In Stock"
  Total inventory increased by 850 units (34 × 25)
  15 previously unavailable items now accepting orders

Claude Reports: “Inventory updated! All 34 products in your Summer Collection now have 25 additional units (850 total added). The 15 products that were out of stock are now available for ordering. Your store is ready for weekend sales!”

Time Saved: 6 seconds vs. 30-45 minutes of manual inventory updates

Additional Benefit: No mistakes! When you’re tired at the end of the day, manually updating 34 products means you might:

• Forget to change some from “out of stock” to “in stock”
• Type the wrong quantity (25 vs. 52)
• Miss some products entirely
• Accidentally change the wrong field

Claude does it perfectly, every time, in seconds.

The Power of Orchestration

These examples demonstrate key advantages:

• Speed: Operations that take 30 minutes or 2 hours manually complete in 6-15 seconds
• Accuracy: No typos, no skipped steps, no accidentally changing the wrong thing
• Consistency: Everything follows your established patterns and rules
• Context-Awareness: Claude uses your actual site structure, not generic templates
• Bulk Operations: Processing 50, 100, or 500 items with single commands
• Reduced Friction: Instead of switching between multiple admin screens, clicking through menus, copying and pasting—you just describe what you want

With full MCP implementation (Tools + Resources + Prompts), these workflows become even more powerful—automatically adapting to your specific site configuration, following your documented standards, and executing complex procedures through simple conversational commands.

Why This Matters for Different People

For Solo Site Owners: You can manage your site by talking to Claude in plain English instead of clicking through dozens of admin screens. No more “Wait, where’s that setting again?” or “How do I do this without breaking something?”

For Small Business Teams: Everyone on your team can execute complex workflows consistently, even if they’ve never used WordPress before. Your processes become as simple as “Run the weekly newsletter workflow.”

For Developers: MCP transforms WordPress from a GUI-driven platform into a programmable API that AI can orchestrate. Complex migrations, bulk operations, and repetitive tasks become conversational. You write the tools once, then let Claude figure out how to combine them for any task.

For Agencies: Client onboarding compresses from hours to minutes. Each client’s unique setup is documented in resources, workflows are encoded in prompts, and any team member can deliver consistent results. When a client says “Update all our product descriptions to mention our new warranty,” you can say “Done” in 30 seconds.

Current Implementation: 133 Abilities Across Four Integrations

This WordPress MCP Server currently implements the “Tools” layer of MCP (called “Abilities” in the codebase) with 133 total capabilities:

• Core WordPress (79 abilities): Posts, pages, media, users, comments, taxonomies, menus, themes, plugins, and site configuration
• WooCommerce (10 abilities): Products, orders, stock management, refunds, and order notes
• Advanced Custom Fields (34 abilities): Field groups, field definitions, repeaters, flexible content, options pages, and bidirectional relationships
• Blockhead FSE Theme Builder (10 abilities): Child themes, brand setup, templates, template parts, patterns, and theme.json configuration

What This Means Practically: Right now, Claude can perform 133 different WordPress operations on your behalf. That’s 133 things you can ask Claude to do, and it will understand and execute them—from creating a single blog post to orchestrating a complete site redesign.

Future Development: Resources and Prompts represent the next evolution. Resources would give Claude comprehensive context about your specific site (“Here’s how my site works”), while Prompts would encode your frequent workflows into one-command operations (“Run my complete product launch checklist”).

Getting Started

The Model Context Protocol represents a fundamental shift in how we interact with WordPress. Instead of learning where every button and menu lives in wp-admin, you can simply describe what you want in plain English and let AI handle the implementation.

Whether you’re managing content, building themes, running an e-commerce store, or handling complex custom field structures, MCP makes WordPress conversational—and far more accessible to everyone.

Ready to see it in action? Ask Claude to demonstrate any of the 133 available WordPress abilities. Try saying: “Create a draft blog post about [your topic]” or “Show me all my published posts from last month.”