Skip to main content
Glama
AI Workbench MCP

AI Workbench MCP

by alptugharun

Related Servers

Alternatives to AI Workbench MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Exposes an agent skill, reference guides, and Blender Python script templates over stdio so AI agents can follow a structured modeling workflow and retrieve validation/export resources. It does not itself control a live Blender scene and must be paired with a separate Blender-control MCP server for live operations.
      7
      MIT
    • A
      license
      A
      quality
      Not graded
      maintenance
      Universal AI Agent OS — governed skills, rules, and commands for AI coding assistants (Claude Code, Augment, Cursor, Copilot, Windsurf). Read-only MCP bridge serves prompts and resources from a release-pinned content bundle.
      26
      1,196 npm
      18
      MIT
    • F
      license
      B
      quality
      C
      maintenance
      Connects an LLM to specialized MCP servers via stdio, enabling authenticated GitHub repository, issue, file, and code operations alongside TF-IDF retrieval over employee PDF records and QA test-case generation and result validation. It exposes tools, a read-only resource, and reusable prompt templates so a client can discover and orchestrate multiple capabilities in one workflow.
      3
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves skill-defined JSON-in/JSON-out scripts as callable tools over MCP stdio, driven by a portable skill-runtime.json manifest that supplies each tool's title, description, and input schema. Exposes commands to validate, list, and run skills, so hosts can discover and invoke agent skills without custom per-skill glue code.
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.
      2
      MIT

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: list_prompts enumerates the catalog, render_prompt renders a specific template, and get_assistant retrieves a blueprint. The list vs get distinction is clear, with no overlapping purposes.

    Naming Consistency5/5

    All names follow a consistent verb_noun snake_case pattern: list_prompts, render_prompt, get_assistant. Pluralization varies logically (list many vs render/get one), but the convention is uniform.

    Tool Count5/5

    Three tools are well-suited to a read-only local catalog, covering the essential operations of enumerating, rendering, and retrieving. The count is minimal but each tool earns its place, with no bloat or missing core function.

    Completeness4/5

    The surface covers listing, rendering, and retrieving, but lacks a direct way to get a raw prompt template without rendering it (e.g., get_prompt) or a generic assistant blueprint without host selection. These are minor gaps for a small catalog that agents can likely work around.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive