Skip to main content
Glama
estebanstifli

WordPress MCP Hub

by estebanstifli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to WordPress MCP Hub

No user-submitted related servers found.

    Related Servers

    • JalinWP

      fatomate
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP gateway that enables AI clients to securely connect to WordPress and WooCommerce sites via OAuth, retrieve permitted content and data, and apply changes under configurable approval modes.
      GPL 2.0

    • TypeScript WordPress MCP

      bokazio
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for WordPress content management that provides a secure interface for AI assistants to interact with WordPress sites, enabling content creation, editing, and media management without destructive operations.
      MIT

    • maza

      prasanth263
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP gateway that lets MCP clients connect once and then discover and execute tools across multiple MCP servers, with centralized credential management, per-tool access control, CLI, and dashboard.
      MIT

    • MCP-ToolHub

      Frz2004
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a unified MCP gateway enabling AI agents to securely access multiple tool servers (knowledge base, database, repo, etc.) with dynamic tool selection and OAuth2/RBAC security.
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools are clearly distinct by scope (one site vs all sites) and action (list, get, test, call, diagnose). However, test_site_connection, list_site_tools, and diagnose_sites overlap around connectivity and tool discovery, which could cause occasional misselection.

    Naming Consistency5/5

    All tool names use consistent snake_case with a verb-first pattern (list_, get_, test_, call_, diagnose_) and include 'site' or 'sites' where relevant. The convention is predictable throughout.

    Tool Count5/5

    Six tools is well-scoped for a hub that manages configured WordPress MCP sites, tests connectivity, discovers remote tools, and invokes them. Each tool has a clear role without redundancy.

    Completeness4/5

    The set covers listing, getting, testing, discovering remote tools, calling remote tools, and diagnosing sites. Minor gaps exist around site lifecycle management (create/update/delete configured sites) and credential handling, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources