Connect your AI to WordPress

Give Claude, ChatGPT, Mistral or any MCP client secure access to WordPress — no official WordPress MCP server required. Proxoria turns WordPress's API into tools your AI can use, with per-user authentication and write actions gated by your approval.

What your AI can do with WordPress

Once connected, these tools appear automatically in your AI assistant:

  • searchread-only

    Full-text search across the site's content (posts, pages…). Returns matching items with their type and id.

  • list_postsread-only

    List blog posts (published by default), optionally filtered by full-text search or status (draft, pending, publish).

  • get_postread-only

    Get a post by id (title, content, status, categories).

  • create_postwrite · needs approval

    Create a blog post as a DRAFT — a human reviews and publishes from WordPress. Writes to the site, so it goes through the confirmation guardrail when enabled.

  • update_postwrite · needs approval

    Update a post's title, content or excerpt. Deliberately cannot change the status: publishing stays a human action in WordPress. Writes to the site, so it goes through the confirmation guardrail when enabled.

  • list_pagesread-only

    List the site's pages, optionally filtered by full-text search.

  • get_pageread-only

    Get a page by id (title, content, parent).

  • create_pagewrite · needs approval

    Create a page as a DRAFT — a human reviews and publishes from WordPress. Pages are structural site content (home, about, legal…). Writes to the site, so it goes through the confirmation guardrail when enabled.

  • update_pagewrite · needs approval

    Update a page's title or content. Deliberately cannot change the status: publishing stays a human action in WordPress. Writes to the site, so it goes through the confirmation guardrail when enabled.

  • list_commentsread-only

    List comments, optionally those of one post.

  • list_categoriesread-only

    List the site's categories (ids are used by create_post).

  • list_mediaread-only

    List the media library (images, files), optionally filtered by search.

  • get_mediaread-only

    Get one media item: its file URL, sizes, alt text and the post it is attached to.

  • list_tagsread-only

    List the site's tags (ids are used by create_post and update_post).

  • create_termwrite · needs approval

    Create a category or a tag. Writes to the site, so it goes through the confirmation guardrail when enabled.

  • list_usersread-only

    List the site's users — the authors a post can be attributed to, with their roles when the credential is allowed to see them.

  • create_commentwrite · needs approval

    Post a comment on an article. It follows the site's moderation rules, so it may land as pending rather than published. Writes to the site, so it goes through the confirmation guardrail when enabled.

  • moderate_commentwrite · needs approval

    Moderate a comment: approve it, put it back on hold, mark it as spam or send it to the trash. Writes to the site, so it goes through the confirmation guardrail when enabled.

  • list_post_revisionsread-only

    List the saved revisions of a post — who changed it and when — so an edit can be traced or compared.

  • trash_postwrite · needs approval

    Send a post to the trash. WordPress keeps it there rather than deleting it, so it can be restored from the admin. Writes to the site, so it goes through the confirmation guardrail when enabled.

  • get_site_settingsread-only

    Read the site's own settings: title, tagline, language, timezone, date format, default category and whether new posts are open to comments.

  • list_pluginsread-only

    List the plugins installed on the site with their version and whether they are active (needs an administrator credential; WordPress refuses it otherwise).

  • list_content_typesread-only

    List the content types this site registers — posts and pages, plus whatever its theme and plugins add (products, events, portfolios…). Each one's `rest_base` is what list_custom_content takes.

  • list_custom_contentread-only

    List entries of a custom content type, for the long tail a dedicated tool would not cover: pass the `rest_base` that list_content_types reported (e.g. 'product', 'tribe_events'). Reads only.

Example prompts

Just ask your AI in plain language — it picks the right WordPress tool:

  • Draft a post from these release notes, put it in the right category and tag it, but leave it as a draft.
  • Which comments are waiting for moderation, and which of them look like spam?
  • List every page with no content since last year, so we can decide what to prune.
  • Who wrote what over the last month, and which posts were revised after publication?
  • Which plugins are installed but inactive, and what does the site's settings say about its language and timezone?

How it works

  1. Create your Proxoria account and add your MCP endpoint to Claude or ChatGPT.
  2. Connect WordPress with your API key — each user connects their own account, credentials encrypted at rest.
  3. Your AI instantly gets the WordPress tools. Write actions wait for your approval in the dashboard before anything changes.

Frequently asked questions

Does WordPress have an official MCP server?
You don't need one. Proxoria exposes WordPress to your AI through the Model Context Protocol, so you can use it from Claude, ChatGPT, Mistral or any MCP-compatible client — no official WordPress MCP server required.
What can my AI do with WordPress through Proxoria?
It gets 24 tools: search, list_posts, get_post, create_post, update_post, list_pages, get_page, create_page, update_page, list_comments, list_categories, list_media, get_media, list_tags, create_term, list_users, create_comment, moderate_comment, list_post_revisions, trash_post, get_site_settings, list_plugins, list_content_types, list_custom_content. For example, full-text search across the site's content (posts, pages…). returns matching items with their type and id.
Is the WordPress connector read-only?
No — it can also make changes. Write actions go through Proxoria's confirmation guardrail by default: your AI proposes them, and you approve each one from your dashboard before anything is written to WordPress.
How do I connect WordPress to my AI?
Create a Proxoria account, connect WordPress with your API key, and add your Proxoria MCP endpoint to Claude or ChatGPT. Your AI instantly gains the WordPress tools.

Ready to connect WordPress to your AI?

Set it up in minutes — no code, secure by default.

Get started free

About Proxoria. Proxoria connects AI assistants — Claude, ChatGPT, Mistral and any Model Context Protocol (MCP) client — to the business apps you already use, turning each app's API into tools your AI can call, with per-user authentication and write actions gated by human approval.