CloseHub Connector

Plugin Specification

WordPress.org Official Data

Developer	Close·technology
Version	v1.1.2
Active Installs	20 +
Requires / Tested	6.4 / 7.1.1
Last Updated	2026-09-18 8:05am GMT
Official Link	View Details ->

CloseHub Connector replaces the multiple credentials previously required to link a WordPress site with CloseHub — a marketing project management platform.

Once the plugin is activated, it generates a secure API key and exposes a dedicated REST API namespace (/wp-json/closehub/v1/) that CloseHub uses to interact with your site.

It also exposes content abilities through the WordPress MCP Adapter. MCP clients can discover, list, read, create, update, update a post slug, replace one exact Gutenberg block, and send posts to the trash using the server at /wp-json/mcp/mcp-adapter-default-server. closehub/update-post-slug accepts a post ID and slug, then returns the normalized unique slug and resulting URL. closehub/get-post returns a content_hash; use it with closehub/replace-gutenberg-block, a zero-based block_path, the current block name, and one replacement serialized block so a stale read cannot overwrite newer content. These abilities default to the post type but accept a post_type input for any other post type registered with an admin UI — pages, WooCommerce products (including product types WooCommerce’s own MCP abilities don’t support, such as subscriptions), or custom post types. Authenticate with a WordPress user account that has the required post capabilities; the CloseHub API key is not used for MCP authentication.

For WooCommerce, MCP clients with the manage_woocommerce capability can retrieve an order summary for a date range, including order count, total sales, average order value, and matching orders.

It also exposes a set of “site” abilities for the CLOSE web go-live checklist — configuration steps that used to be manual or wp-cli only. Each requires the WordPress capability noted below.

Available MCP site abilities:

• closehub/search-replace-domain (manage_options) — Replace old_domain with new_domain across post content, options, comments, and meta tables, re-serializing serialized values safely. Skips wp_posts.guid. Pass dry_run: true to preview the number of rows that would change per table without writing anything. Example: { "old_domain": "staging.example.com", "new_domain": "example.com" }.
• closehub/set-robots-txt (manage_options) — Write content to robots.txt, physically if the site root is writable, otherwise served virtually through the robots_txt filter. Example: { "content": "User-agent: *nDisallow:nSitemap: https://example.com/sitemap.xml" }.
• closehub/set-post-noindex (edit_post on the target post_id) — Set or clear the noindex robots meta for one post/page using whichever SEO plugin (Rank Math or Yoast) is active. Example: { "post_id": 42, "noindex": true }.
• closehub/flush-permalinks (manage_options) — Regenerate rewrite rules, equivalent to wp rewrite flush. Takes no parameters.
• closehub/get-htaccess (manage_options, read-only) — Return whether .htaccess exists and its current content. Takes no parameters.
• closehub/set-site-settings (manage_options) — Update the site timezone and/or admin email; at least one is required. Example: { "timezone": "Europe/Madrid", "admin_email": "[email protected]" }.
• closehub/reassign-posts-author (edit_others_posts) — Reassign every post of post_type (default post) from from_author_id to to_author_id, with a per-post success result. Example: { "from_author_id": 3, "to_author_id": 1 }.
• closehub/install-wp-org-plugin (install_plugins) — Install (without activating) a plugin from the WordPress.org plugin directory by slug. Example: { "slug": "two-factor" }.
• closehub/list-unused-plugins (activate_plugins, read-only) — List installed plugins that are not currently active, as removal candidates. Takes no parameters.
• closehub/update-plugins-and-core (update_plugins and update_core) — Update every plugin with an available update and WordPress core to the latest version, with a per-plugin success result. Takes no parameters.
• closehub/create-site-user (create_users, plus promote_users when role is administrator) — Create a WordPress user for the site’s client. role defaults to editor; username defaults to the local part of email when omitted. Example: { "email": "[email protected]", "role": "editor" }.

What it replaces:

• WordPress Application Password (username + password)
• WooCommerce REST API consumer key and consumer secret
• Gravity Forms API key

You only need to share two things with CloseHub:

1. Your site URL
2. The generated API key (found at Settings → CloseHub)

Available endpoints:

• GET /closehub/v1/ping — verify the connection
• POST /closehub/v1/posts — publish or draft a post (or another post type via post_type), including optional SEO metadata (Rank Math or Yoast), featured image, and categories
• PUT /closehub/v1/posts/{id} — update a post’s (or other post type’s) title, content, excerpt, status, SEO metadata, featured image, or categories
• GET /closehub/v1/woocommerce/orders — fetch order data (requires WooCommerce)
• GET /closehub/v1/gravity-forms/forms — list forms (requires Gravity Forms)
• GET /closehub/v1/gravity-forms/forms/{id} — get form details
• GET /closehub/v1/gravity-forms/forms/{id}/entries — count form entries by date range

WooCommerce and Gravity Forms endpoints return a clear error if those plugins are not active — they are not required.

Multisite networks:

On a WordPress Multisite network, the same endpoints listed above are shared by every site in the network — there is no separate namespace or key to manage. Activate the plugin network-wide and go to Network Admin → Settings → CloseHub to find one API key shared by the whole network. Every request to those endpoints automatically returns a sites array with one entry per site in the network (site_id, url, and that site’s data or an error message), instead of a single site’s result — handy when a network is used to run the same company in multiple languages.