Skip to main content
Glama
DollhouseMCP

DollhouseMCP

by DollhouseMCP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to DollhouseMCP

No user-submitted related servers found.

    Related Servers

    • GitHub MCP Server

      aviralkaushik412
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that connects Claude AI directly to the GitHub API, enabling natural language queries for live repository data, issues, PRs, and contributions.
      1
      -

    • GitHub MCP Server

      wulfitect
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that provides comprehensive GitHub integration for Claude Desktop, allowing users to manage repositories, issues, and pull requests. It supports file operations, branch management, and repository searches through natural language commands.
      385 npm
      -
    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.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    The five top-level tool names create/read/update/delete/execute map to clearly distinct CRUD-style actions, so misselection between tools is generally unlikely. However, mcp_aql_read is not truly read-only (it includes activate_element, deactivate_element, open_portfolio_browser, and permission_prompt), and mcp_aql_create bundles auth and deadlock operations, creating minor boundary ambiguity.

    Naming Consistency4/5

    Tool names follow a highly consistent mcp_aql_<verb> pattern, and most sub-operations use verb_noun snake_case. The pattern is not perfect because a few operations like addEntry, portfolio_element_manager, and beetlejuice_beetlejuice_beetlejuice break convention.

    Tool Count4/5

    Five tools is a reasonable surface size and maps neatly to a CRUD-plus-execution lifecycle. The count is slightly coarse for the server's actual breadth because each tool is a mega-router exposing dozens of operations, especially mcp_aql_read.

    Completeness4/5

    The set covers element CRUD, execution lifecycle, auth/OAuth, collections, portfolio, logs/metrics, and self-discovery, so most workflows have a path. Minor lifecycle edges such as explicitly removing from a portfolio/collection or listing all executions are not clearly surfaced, but they are not critical dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources