← All add-ons

MxChat MCP Server

Version 1.0.5 · Updated 1 day ago

Expose your MxChat install as a Model Context Protocol server so Claude, ChatGPT, and any MCP-aware agent can list transcripts, inspect bots, and push knowledge — natively, no per-message fees.

Features

  • JSON-RPC 2.0 endpoint at /wp-json/mxchat-mcp/v1/mcp speaking the MCP spec
  • Bearer-token auth that reuses your MxChat REST API token — no second secret to manage
  • Read-only or admin role gating from a dedicated MxChat → MCP Server admin page
  • Connect snippets for Claude Code, ChatGPT desktop, and mcp-inspector with one-click copy
  • Tool set focused on chatbot ops: bot_info, list_transcripts, search_transcripts, list_knowledge, add_knowledge
  • WooCommerce extension: list_products, get_product, list_orders, get_order, search_customers

What's new

Version 1.0.5

  • New MCP Connection Test v2 — the "Test endpoint" button on the Endpoint tab now runs two probes: the original loopback test plus a second probe that mimics the headers an external MCP client (claude.ai, Claude Code) sends. A host-level WAF that intercepts external traffic (Cloudflare, Sucuri, Wordfence, SiteGround, WP Engine's default) shows up at setup time with a clear "WAF-blocked" pill and a fix hint, instead of silently passing in admin but failing the first time you try to connect from claude.ai.
  • New "Test from your own machine" disclosure on the Connect tab — a copyable curl command that mimics claude.ai, so you can verify from your laptop's ISP whether the endpoint is reachable externally. Useful when the in-admin external probe is inconclusive.
  • Improved Admin page assets cleaned up — the inline `<style>` and `<script>` blocks that used to live at the bottom of the MCP admin page are now in their own `css/admin-mcp.css` and `js/admin-mcp.js` files. Browsers can cache them between page loads, and the admin page renders identically to before.
  • Improved The static bearer token controls on the Connected Apps tab (Reveal / Copy / Regenerate) are now collapsed by default behind an "Advanced: Static bearer token (CLI / CI fallback)" disclosure. OAuth is the primary visible auth path; the legacy bearer token surface is opt-in. The underlying bearer-token code path is unchanged — CLI / CI clients still work exactly as before.
  • Improved "Connect a client" tab now leads with OAuth — the Claude Code and ChatGPT cards show the OAuth-first snippets (no bearer header), with a clear "browser opens to authorize" hint. The static bearer token snippets for Claude Code and mcp-inspector now live behind an "Advanced: Static bearer token (CLI / CI fallback)" disclosure, and the snippets auto-fill the actual bearer token when one is configured (replacing the YOUR_TOKEN placeholder) so copy-paste just works.
  • Fixed Claude Code "claude mcp add" snippets now include the required `--transport http` flag. Without it, Claude Code treats the command as a stdio MCP server and the connection fails. Existing customers who hit this can re-copy the corrected snippet from the Connect a client tab.
  • Fixed Sidebar version badge now always matches the plugin header. The `MXCHAT_MCP_VERSION` constant is derived from the plugin's own `Version:` field via `get_file_data()` instead of being hardcoded — eliminates a class of "version drift" bugs where the badge could lag the actual installed version.