The workflow library

Good work starts with a clear recipe.

Six practical ways to use MCPWP with your assistant. Every recipe includes prerequisites, a prompt, and the evidence to look for. These are guides, not claims that every client and site combination has been tested.

Six recipes. Choose one small task to begin.

Start here

Connect Claude. Verify your first site read.

Give Claude the context of your WordPress site, then prove it is reading the right one.

Start here

Connect ChatGPT. Start with one clear check.

Connect your site, inspect the available tools, and confirm exactly what ChatGPT can read.

Create content

Turn approved notes into a WordPress draft.

Move from source material to a useful article with its claims, links and review questions intact.

Improve a page

Improve one Elementor section with a clear review.

Keep the page structure you already have while preparing one precise, visible improvement.

Improve discovery

Find useful internal links before adding them.

Make a small, evidence-backed link plan that helps readers reach the next useful page.

Run a store

Review a small product catalogue for missing details.

Spot gaps in product information without touching prices, stock or orders.

Start here

Connect Claude. Verify your first site read.

Receive the correct site name and URL from a real MCPWP read before authorizing any edits.

Before you begin

  • Permission from the site owner to connect Claude.
  • MCPWP installed and active on the intended site; copy its exact MCP endpoint from Setup.
  • A Claude account with custom connector access and a remote endpoint reachable by Claude.

Start with the narrowest available read access. Review the connection grant yourself; never paste credentials into a prompt.

Follow the steps

  1. In Claude, open Customize → Connectors and add a custom connector. Organization owners may need to add it first.
  2. Enter a clear site name and the exact MCP endpoint from MCPWP Setup. Review the detected authentication and complete the supported sign-in flow.
  3. Enable this connector in the conversation. Check the discovered tools before using the prompt below.
  4. Request site information only. Compare the returned URL and site name with your intended WordPress site. Save that result as your first checkpoint.

A prompt to adapt

Use only the MCPWP connection for [SITE URL]. First discover the available tools, then read site information. Return the site name, canonical URL, WordPress version and available content tools from the response. Make no changes. If the URL is different, authentication fails, or a required read tool is unavailable, stop and explain the next owner action. Do not guess missing values.

What a good result includes

  • A successful site-information tool response naming the expected site.
  • The returned URL matches the site you intended to connect.
  • No content-write tool was called.
Limits and things to check
  • A connection badge alone is not a successful site read.
  • Claude account and organization controls affect access. Remote connectors connect from Anthropic infrastructure.
  • This recipe follows official client guidance; the project evidence reviewed here proves an actual Codex first read, not a Claude end-to-end acceptance test.

Guidance checked 15 November 2026. Get started with custom connectors using remote MCP

Start here

Connect ChatGPT. Start with one clear check.

Use the correct MCPWP connection in ChatGPT and verify the site identity without changing WordPress.

Before you begin

  • MCPWP installed and active; the exact endpoint copied from the site’s Setup screen.
  • A ChatGPT account or workspace that permits custom MCP connections.
  • Owner authorization and any required workspace administrator access.

Approve only the access needed for the first read. A WordPress license key is not a connection credential.

Follow the steps

  1. On ChatGPT web, open Plugins, select the plus button, then Add custom MCP server. If your account shows the legacy Apps experience, follow OpenAI’s linked legacy instructions.
  2. Enter the name and exact HTTPS MCP endpoint. Configure the supported authentication, review the warning and discovered tools, then create the plugin.
  3. Install the resulting plugin and select it with @ in a new conversation.
  4. Run the read-only prompt below. Compare the returned site identity with your intended site before discussing edits.

A prompt to adapt

Read the connected WordPress site through [MCPWP CONNECTION NAME]. Discover its available tools and call the site-information read tool. Show the site name, URL and the permissions or limitations the response actually reports. Make no changes. Do not infer that write access exists because connection succeeded. Stop on an unexpected site or access error and tell me what needs attention.

What a good result includes

  • A tool result from the selected MCPWP connection, not a general answer about WordPress.
  • The correct site name and URL.
  • A clear distinction between tools discovered and actions actually tested.
Limits and things to check
  • OpenAI currently documents full MCP support for Business and Enterprise/Edu on web, with Pro limited to read/fetch. Workspace rules still apply.
  • The current Plugins flow does not require Developer Mode first; older instructions may describe a different interface.
  • This is source-backed setup guidance, not a claim that this project has completed a fresh ChatGPT connection test.

Guidance checked 15 November 2026. Connecting custom MCP servers in ChatGPT

Create content

Turn approved notes into a WordPress draft.

Create one native Gutenberg draft that an editor can review without reconstructing the source material.

Before you begin

  • A connected client with draft-writing tools available.
  • An approved brief, source material and named reviewer.
  • The site’s brand guidance and an agreed article slug.

Authorize one new draft only. Publication, scheduling and changes to existing articles require separate approval.

Follow the steps

  1. Read site information and brand guidance. Confirm Gutenberg is the intended editor.
  2. Search the proposed slug and title to avoid creating a duplicate. If a draft already exists, stop and ask whether to revise it.
  3. Prepare an outline from the supplied sources. Mark unsupported claims as questions rather than filling them in.
  4. Create one draft with native blocks and explicit draft status. Record the returned post ID immediately.
  5. Read the saved post back, compare its claims and links with the sources, and open a preview on desktop and mobile. Give the reviewer the draft link and unresolved questions.

A prompt to adapt

Use [APPROVED NOTES] to prepare one Gutenberg article for [SITE URL] about [TOPIC], for [AUDIENCE]. Read the site context first and check whether [SLUG] already exists. Use only supported facts; keep source links and flag gaps. You may create one post with status draft. Do not publish or schedule it. Record its ID, read back the saved content, and give me the preview link, source list and review questions. If creation times out, search for the draft before retrying; never create a second copy blindly.

What a good result includes

  • Saved post ID, edit or preview URL, and a read-back status of draft.
  • Source links supporting factual claims and a list of unresolved questions.
  • A rendered preview checked for headings, links and small-screen readability.
Limits and things to check
  • AI-generated text still needs editorial and factual review.
  • Draft visibility depends on credential permissions; use an authorized editor to review private content.
  • A successful save does not prove the public page looks correct or that it has been published.

Improve a page

Improve one Elementor section with a clear review.

Prepare a focused change on an existing draft or staging page and show the reviewer exactly what changed.

Before you begin

  • Elementor active and its current layout mode checked.
  • An owner-designated draft or staging copy with a known page ID.
  • A saved before snapshot of the target widget, page structure and relevant settings.

Edit only the agreed section on the designated review copy. Live pages, global styles, forms, menus and display conditions remain outside this recipe.

Follow the steps

  1. Read the Elementor status and structural summary. Confirm the page ID, draft or staging status, and target widget ID.
  2. Capture the original widget settings and identify the exact text or style change. Preserve existing forms, tracking and functional links.
  3. Apply a focused widget edit. Avoid replacing the entire page or creating a theme template for this task.
  4. Read the widget and page status back. Compare with the before snapshot.
  5. Render the review copy on desktop and mobile. Check wrapping, contrast, navigation and any affected interactions; hand over the preview and before/after notes.

A prompt to adapt

On review page [PAGE ID] at [SITE URL], improve only [SECTION] to achieve [GOAL]. First verify this is the approved draft or staging copy, read Elementor status and the structural summary, and save the current target settings. Use a focused widget edit; preserve IDs, links, forms and global settings. Do not publish, change display conditions or create a theme template. Read back the changed settings and report the preview URL, exact before/after change, and desktop/mobile checks. Stop if the page changed since your first read.

What a good result includes

  • The exact review page and widget IDs.
  • Before/after settings with only the authorized change.
  • Read-back status and desktop/mobile visual evidence.
Limits and things to check
  • Rendered HTML alone does not establish visual or interaction quality.
  • Widgets supplied by other plugins may need a different supported edit path.
  • Review-copy success does not authorize or prove live publication.

Run a store

Review a small product catalogue for missing details.

Give the store owner a prioritized list of content improvements for up to ten WooCommerce products.

Before you begin

  • WooCommerce active and its MCPWP tools available.
  • An owner-approved category or list of product IDs, limited to ten products.
  • Authoritative product specifications for checking claims.

Read product records only. No changes to orders, customers, inventory, prices or public descriptions.

Follow the steps

  1. Confirm the site and WooCommerce status. Resolve the requested products to exact IDs.
  2. Read each product’s description, images, attributes and variations. Collect only the fields needed for the review.
  3. Compare descriptions with supplied specifications. Flag missing details and contradictions; do not invent materials, compatibility or performance claims.
  4. Prepare suggested copy separately from the live product, ordered by customer impact. Include a product ID and source for each proposed change.
  5. Have the owner approve exact edits before any write. After approved changes, verify the saved product fields and public render separately.

A prompt to adapt

Review up to ten products in [CATEGORY OR PRODUCT IDS] on [SITE URL]. Use product reads only. Compare descriptions, images and attributes against [APPROVED SPECIFICATIONS]. Return a table of product ID, observed gap, customer impact, suggested correction and source. Put missing evidence in a question for the owner. Do not change prices, stock, orders, customers or product content, and do not retrieve customer records.

What a good result includes

  • A bounded list of reviewed product IDs.
  • Observed fields and source-backed corrections, with uncertain claims labelled.
  • No product, order, stock or customer mutation.
Limits and things to check
  • The review covers only the selected products and supplied specifications.
  • Product extensions and variation structures can affect available fields.
  • A content review does not validate checkout, payment, fulfillment or product safety.

Thinking beyond a single session?

Explore our proposed design for work that can pause, resume, and keep a trustworthy record.