AbleSign MCP
Related Servers
Alternatives to AbleSign MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server for controlling LED displays via MQTT. It enables AI agents to list devices and send text, images, colors, or clear commands with authentication and permission checks.-
- AlicenseNot gradedqualityDmaintenanceA full-featured MCP server providing seamless access to CustomGPT.ai APIs, enabling agent and conversation management through MCP-compatible clients.5MIT

Mediagraph MCPofficial
AlicenseCqualityCmaintenanceExposes the Mediagraph digital asset management API as an MCP server, enabling AI agents to search, organize, tag, and manage media assets through natural language.1007 npmMIT- AlicenseAqualityCmaintenanceMCP server for multi-agent AI systems providing mailbox messaging, A2A task delegation, resource coordination, and a web dashboard.216 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP (Multi-Agent Conversation Protocol) Server that enables interaction with the At-Work API (api.at-work.biz), allowing agents to communicate with this service through various transport modes like stdio, SSE, and HTTP.-
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with QUADS infrastructure systems via API, enabling resource management and automation through LLM applications.MIT
TDQS
Scored across 44 tools
Each tool targets a distinct resource and action. Media upload/replacement have separate initiate and complete steps. Screen playlist operations (save, add, update) are clearly differentiated. No ambiguity between tools.
All tools follow a consistent verb_noun pattern in snake_case (e.g., list_media_files, create_web_app, delete_screen). Verbs like list, create, get, update, delete, initiate, complete, register are used predictably.
44 tools is excessive for a single server, far exceeding the typical well-scoped range of 3-15. Many operations could be consolidated or split into separate servers.
The tool set covers all major entities (media, web apps, screens, screen groups, folders, workspaces) with full CRUD and specialized operations like upload flows and playlist management. Minor gaps exist (e.g., no user management beyond workspace users), but core workflows are well-supported.