Skip to main content
Glama
VeloCMS

velocms-mcp

by VeloCMS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to velocms-mcp

No user-submitted related servers found.

    Related Servers

    • notipo

      kfuras
      A
      license
      A
      quality
      A
      maintenance
      MCP server for publishing to WordPress. 13 tools cover posts, categories, tags, image hosting, featured images, and SEO metadata (Rank Math, etc.) One call runs the full markdown-to-live-URL pipeline.
      13
      11 npm
      4
      AGPL 3.0

    • blogger-mcp

      tutul
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to manage Google Blogger blogs via the Blogger API v3, including listing and searching posts, creating drafts, editing, publishing or scheduling posts, managing static pages, and moderating comments.
      18
      MIT

    • AlphaBridge MCP

      CultureClub-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns a WordPress site into a native MCP server: 39 structured tools for content, media, taxonomies, comments, widgets and site settings, with OAuth 2.1 + PKCE and per-call WordPress capability checks. Pure PHP inside WordPress — no bridge server or middleware to host.
      GPL 2.0

    • wpxmcp

      alokemajumder
      A
      license
      A
      quality
      A
      maintenance
      Enables managing self-hosted WordPress sites from any MCP client, covering content, themes, plugins, menus, users, and SQL with credentials in Cloudflare Worker Secrets or local stdio. It provides 117 tools and adds guardrails like drafts, trash, and dry-run operations.
      117
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: post CRUD, publish state transitions, media listing, comment moderation, member listing, and site settings retrieval. No two tools overlap in purpose.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (get_, create_, list_, update_, delete_, publish_, unpublish_, moderate_). The consistent use of singular/plural nouns is conventional and readable.

    Tool Count5/5

    12 tools is well-scoped for a CMS. Post lifecycle is fully represented, and the addition of media, comments, members, and settings covers the main auxiliary resources without unnecessary bloat.

    Completeness3/5

    Post CRUD and publishing workflow are complete, but media only supports listing, site settings only get, and comments lack deletion. These read-only surfaces create dead ends for agents trying to manage those resources.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources