ClearPost: WordPress SEO Agent

com.clearpostpluginPublished by clearpostplugin.comv1.0.1Updated Oct 25, 2026

SEO agent for WordPress. Grows your organic traffic on autopilot. 14 tools, zero configuration.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint for WordPress that gives an assistant SEO tools to help grow organic traffic, authenticated with a ClearPost license key.

What you can do
Connect an assistant to a WordPress site's ClearPost SEO agent over a remote endpoint, authenticated with a license key sent in the Authorization header. The provider advertises 14 tools and zero configuration, aimed at SEO work on the site. The manifest does not list the individual tools, so the exact actions available are not documented here.
When to use it
Consider it when you run a WordPress site and want an assistant to help with SEO tasks through ClearPost rather than doing them by hand. It is aimed at organic-traffic growth work on the connected site.
Requirements
A remote endpoint at your site domain, reached over streamable HTTP. A ClearPost license key is required as a bearer token in the Authorization header; the provider says it is found in the ClearPost dashboard. A ClearPost account and a WordPress site are implied.
Before you install
The Authorization header carries your ClearPost license key, so treat it as a secret. The tools are not listed, so what the assistant can read or change on your site is unclear; confirm before granting access. The provider markets automatic traffic growth, so expect changes to site content or SEO settings.

Installation

In SourceWeft

  1. Open ClearPost: WordPress SEO Agent in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.