Skip to main content
Glama
vbalagovic

@neuraldraft/mcp

by vbalagovic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @neuraldraft/mcp

No user-submitted related servers found.

    Related Servers

    • WordPress MCP Server

      gaupoit
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage WordPress sites through natural conversation, supporting post creation, content updates, site queries, and draft-to-publish workflows via the WordPress REST API.
      9
      MIT

    • quill-blog

      Mahnoor-shuaib
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to manage a blog directly from an IDE, including drafting, editing, publishing, scheduling, SEO optimization, and analytics tracking through natural language.
      8,053,408 npm
      BSD 3-Clause

    • wp-mcp

      Adi-ty
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects WordPress sites to AI agents, enabling content management through natural language commands via the WordPress REST API.
      14 npm
      2
      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/5.0

    Scored across 38 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair (e.g., list_galleries, get_gallery, create_gallery, update_gallery, delete_gallery). Even closely related tools like register_image and replace_image have clearly separated responsibilities. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (create_, get_, list_, update_, delete_, generate_, register_, etc.). The resource name is always a clear object, making the action predictable from the tool name alone.

    Tool Count2/5

    With 38 tools, this server is well beyond the typical well-scoped range of 3-15 tools. Even accounting for the broad feature set, the sheer number creates a heavy surface that could overwhelm agents and increase misselection risk.

    Completeness3/5

    The core resources have strong CRUD coverage: galleries, pages, and images are well-supported. However, there are notable gaps: components lack an update tool, blog posts have no delete, and translation keys have no update_content. These missing lifecycle operations force workarounds like delete-and-recreate.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources